dual-copy-skill-publish
Skill2 starsChanged 42 days agoMITView on GitHub
Publish a project-born skill into both the consuming project tree and the portable skills library with matching content, index updates, and hash/symlink verification. Use when promoting a project-only skill outward or fixing drift between two git-tracked copies. Not for portable library skills (use symlink via master-planner). Triggers: dual-copy, dual publish, skill publish, project skill sync.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-auditSkill
- agentic-reactorSkill
- agent-orchestratorSkill
- ai-optimizationSkill
- architecture-synthesisSkill
- audit-allow-buildsSkill
- audit-ide-dependenciesSkill
- author-workflow-skillSkill
- bdd-strategizerSkill
- chrome-extension-mv3Skill
- concurrent-cli-agentsSkill
- control-feederSkill
- control-graphSkill
- cursor-transcript-harvestSkill
- cv-promote-guardSkill
- devcontainer-hardenedSkill
- explore-repo-readonlySkill
- finder-reactorSkill
- fix-dependency-securitySkill
- fusion-sageSkill
- git-worktreesSkill
- grok-host-prepSkill
- gt-flowSkill
- higher-order-decision-architectSkill
- looperSkill
- master-plannerSkill
- mvu-refactor-planSkill
- odysseus-navigatorSkill
- project-editor-profileSkill
- react-client-expertSkill
- semantic-markup-cssSkill
- semantic-nameSkill
- session-unit-orderSkill
- shell-kernel-ontologySkill
- skill-rename-propagationSkill
- split-to-prsSkill
- src-tree-reorganizeSkill
- stellar-roadmapSkill
- stellar-spacemapSkill
- subagent-delegationSkill
- subagent-explore-reportSkill
- supply-chain-hardenSkill
- tauri-agenticSkill
- tauri-ipc-debugSkill
- tidy-commit-pushSkill
- upgrade-packagesSkill
- verification-cockpitSkill
- x-agent-resourcesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 71
Default: edit project first when project-born, then strip project-only overlays before library copy
- Distinctive: line 73
Never edit both independently in the same pass
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dual-copy-skill-publish
Load rule: Formal SoT. Prefer one canonical library + symlink for portable skills. This skill applies only when policy requires two git-tracked trees (project-born skill).
// Signature
ProjectSkill ≔ <project>/.agents/skills/<name>/ // or .cursor/skills/
LibrarySkill ≔ {SKILLS_ROOT}/<name>/ // e.g. ~/Work/personal/skills
SoT ≔ single write source per edit pass; then sync
Kind ∈ { project_born, portable_library }
// Axioms
A1 Scope = project_born only — portable skills → symlink ([master-planner](../master-planner/SKILL.md)); never dual-edit portable bodies
A2 After publish: ProjectSkill ≡ LibrarySkill (byte-identical tree) ∨ ProjectSkill → symlink(LibrarySkill) when vendoring allowed
A3 Indexes updated both sides when name/description changes (README, AGENTS.md)
A4 No secrets / absolute home paths in bodies — use ~ or {REPO_ROOT}
A5 Push only with explicit user approval (shared remotes)
A6 Evaluate(δ) ≔ (Correctness, Effectiveness, Efficiency)Related: skill-rename-propagation · master-planner · author-workflow-skill · session-unit-order (example project-born skill).
Use / skip
| Use | Skip |
| skill born in project must stay in project git and land in library git | portable skill → pull-skills.sh / symlink only |
| promoting in-repo skill outward | pure local experiment you will not publish |
| fixing drift between two intentional copies | one-off edit with no publish intent |
dual-editing a portable SKILL.md for one project (use overlays) |
Procedure
1 Orient → 2 Classify kind → 3 Choose SoT → 4 Write → 5 Sync → 6 Indexes → 7 Validate → 8 Commit (push=HITL)1. Orient
echo "PROJECT=$(pwd)"
echo "SKILLS_ROOT=${SKILLS_ROOT:-$HOME/Work/personal/skills}"
ls .agents/skills 2>/dev/null; ls .cursor/skills 2>/dev/null
test -d "${SKILLS_ROOT:-$HOME/Work/personal/skills}/.git"2. Classify
| Kind | Signal | Action |
| project_born | encodes project-only architecture/incident; kept in project git | this skill |
| portable_library | general procedure; lives in skills repo | symlink via master-planner — stop here |
3. SoT for this pass
- Default: edit project first when project-born, then strip project-only overlays before library copy
- Or: edit library first when generalizing an already-portable extract
- Never edit both independently in the same pass
4. Write under SoT
SKILL.md: third-persondescription+ triggers- optional
references/,scripts/,templates/ - meet QUALITY.md
5. Sync other tree
NAME=<skill-name>
SRC=… # SoT
DST=… # other
# dual-copy (two git trees):
rsync -a --delete --exclude .git "$SRC/" "$DST/"
# OR when project may vendor via symlink (portable after promotion):
ln -sfn "$SKILLS_ROOT/$NAME" .agents/skills/$NAMErsync without --delete leaves stale DST files — always --delete when dual-copying.
6. Indexes
- Library README.md catalog row if new
- Project
AGENTS.mdactive-skills table - master-planner packs only if pack-listed
7. Validate
node "$SKILLS_ROOT/$NAME/scripts/validate-skill.mjs" 2>/dev/null || true
# dual-copy (not symlink):
diff -qr "$SRC" "$DST"
# optional hash:
# find "$SRC" -type f -exec sha256sum {} \; | sort | sha256sum8. Commit (each repo separately)
cd "$SKILLS_ROOT" && git add "$NAME" README.md && git status
# commit with conventional message — push only if user requested
cd "$PROJECT" && git add .agents/skills/$NAME AGENTS.md && git statusDone when
- Kind was project_born (or intentional dual-track documented)
- Trees identical or project uses symlink to library
- Catalogs updated
- Validator (if any) passes;
diff -qrclean when dual-copy - Commits created; push only if user requested
Anti-patterns
| ¬ | Do |
| dual-edit portable library skill per project | overlays + symlink |
| edit only project forever | drift; sync or symlink |
cp/rsync without --delete | stale files in DST |
| one commit across two repos | separate histories |
| push secrets / absolute paths | scrub first |
| reinstall archive distill stubs | rewrite as real procedure |
Done_when cmds: diff -qr "$SRC" "$DST" · test -f "$SKILLS_ROOT/$NAME/SKILL.md" · rg -n '^name:' "$NAME/SKILL.md".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

