Como usar
- Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
- Consulte no original as ferramentas, credenciais e ambientes necessários.
- Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/hqhq1025/skill-optimizer --skill skill-generalizerAntes de começar
- A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
- Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.
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-personalizerfirst. - 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.mdconcise; 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
descriptionshould 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.