private-vs-publishable-skill-audit
Audit a private skill, prompt pack, or assistant workflow before publishing it. Use when extracting public reusable method from client, product, team, or repository-specific agent instructions. Mark private vs mixed vs reusable content, rewrite the mixed layer, and gate release o
Install
npx skills add https://github.com/markoblogo/abvx-agent-skills/tree/main/skills/private-vs-publishable-skill-audit
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install markoblogo-abvx-agent-skills@llmmart
git clone https://github.com/markoblogo/abvx-agent-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole markoblogo/abvx-agent-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Private Vs Publishable Skill Audit
Audit a private skill pack before turning any part of it into a public release.
Goal
Separate:
- private operating detail that must stay internal;
- mixed content that needs rewriting;
- reusable method that can be published.
Workflow
- Inventory the source pack
- list skills, references, templates, examples, and policy notes;
- note which files carry product, client, or repo-specific detail.
- Classify each item
private: should not be published;mixed: useful core, but still carries contextual leakage;reusable: already abstract enough to publish.
- Check for leakage
- product names;
- internal role names;
- routes, paths, commands, and runbooks;
- operational constraints that only make sense inside the private system;
- examples that reveal the original environment.
- Rewrite the mixed layer
- remove names and internal identifiers;
- convert narrow examples into generic ones;
- preserve the method, not the original context.
- Run the publication gate
- after cleanup, ask whether the artifact still makes sense outside the source environment;
- if not, keep rewriting or keep it private.
- Package the release set
- publish only the reusable artifacts;
- keep the private source pack separate from the public one.
Release Gate
An artifact is publishable only if both are true:
- it remains useful after private names, paths, and roles are removed;
- it does not expose constraints or operating detail that belong only to the private source.
Final Report
Return the classified inventory, the release-safe set, the rewritten mixed items, and the reasons for anything left private.
Files (abvx-agent-skills)
-
agents
-
openai.yaml 252 B
Loading…
-
-
SKILL.md 2.1 KB
--- name: private-vs-publishable-skill-audit description: Audit a private skill, prompt pack, or assistant workflow before publishing it. Use when extracting public reusable method from client, product, team, or repository-specific agent instructions. Mark private vs mixed vs reusable content, rewrite the mixed layer, and gate release on decontextualization. license: MIT metadata: abvx_status: experimental abvx_origin: original --- # Private Vs Publishable Skill Audit Audit a private skill pack before turning any part of it into a public release. ## Goal Separate: - private operating detail that must stay internal; - mixed content that needs rewriting; - reusable method that can be published. ## Workflow 1. **Inventory the source pack** - list skills, references, templates, examples, and policy notes; - note which files carry product, client, or repo-specific detail. 2. **Classify each item** - `private`: should not be published; - `mixed`: useful core, but still carries contextual leakage; - `reusable`: already abstract enough to publish. 3. **Check for leakage** - product names; - internal role names; - routes, paths, commands, and runbooks; - operational constraints that only make sense inside the private system; - examples that reveal the original environment. 4. **Rewrite the mixed layer** - remove names and internal identifiers; - convert narrow examples into generic ones; - preserve the method, not the original context. 5. **Run the publication gate** - after cleanup, ask whether the artifact still makes sense outside the source environment; - if not, keep rewriting or keep it private. 6. **Package the release set** - publish only the reusable artifacts; - keep the private source pack separate from the public one. ## Release Gate An artifact is publishable only if both are true: - it remains useful after private names, paths, and roles are removed; - it does not expose constraints or operating detail that belong only to the private source. ## Final Report Return the classified inventory, the release-safe set, the rewritten mixed items, and the reasons for anything left private. -
SKILL_CARD.md 1.4 KB
Loading…
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.