mcpbeat

Skill Generalizer

hqhq1025/skill-generalizer

Use when turning local, private, or personal Agent Skills into publishable skills for GitHub, marketplaces, teams, or public sharing, especially when private paths, personal habits, credentials, internal hosts, or user-specific context must be removed.

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
152
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/hqhq1025/skill-optimizer --skill skill-generalizer

The instruction itself

6 sections, as written by the author

Skill Generalizer

Overview

Convert a working local skill into a clean public artifact. The goal is to preserve the reusable technique while removing private context, personal assumptions, and machine-specific setup.

When To Use

  • A user wants to publish, share, promote, open-source, or package a local skill.
  • A skill was born from personal workflows, private repos, local paths, transcripts, remote hosts, or team conventions.
  • The output needs to be useful to strangers without leaking the author's environment.

Do not use for tuning a skill only for the user's own machine; use skill-personalizer for that.

Workflow

  • Inspect the actual source skill and nearby repo files before judging.
  • If the source skill quality is unclear, run the audit checks from skill-personalizer first.
  • Separate the reusable capability from personal implementation details.
  • Redact or replace private names, paths, hosts, credentials, account IDs, transcripts, and one-off project facts.
  • Rewrite the skill around general triggering conditions, portable workflows, and bounded assumptions.
  • Keep SKILL.md concise; move long rubrics, examples, or scripts into bundled resources.
  • Check target-agent compatibility before writing install instructions or support claims.
  • Produce publication-ready packaging and honest promotion copy only when requested.
  • Verify frontmatter, file layout, install path, and at least one realistic usage prompt.

Public Release Rules

  • Frontmatter description should describe when to use the skill, not summarize its workflow.
  • Public examples must be generic or explicitly sanitized.
  • Claims in README or marketplace copy must match files that actually exist.
  • Prefer portable commands and path placeholders over the author's home directory or private aliases.
  • If a personal detail is essential, turn it into a configurable variable with setup guidance.

References

Read publication-rubric.md when doing a full release pass, redaction review, README rewrite, or promotional packaging.

Read platform-compatibility.md before claiming support for Codex, Claude Code, Cursor, OpenCode, Gemini CLI, or other coding agents.

How to use it

Copy the folder

Take hqhq1025/skill-generalizer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.