tq-forge-promote
Skill8 starsChanged 5 months agoMITView on GitHub
Promote a sandboxed forged skill or agent from $TQ_FORGE_HOME/sandbox/ into production at $CLAUDE_SKILLS_DIR, re-scoring first and refusing anything below 7/10 or failing dry-test. Use when asked for "/tq-forge-promote", "ship the skill", "install the agent", or "move from sandbox to production".
In this repository17 other files it gives its agents.
- handoffSkill
- keep-warmSkill
- savingsSkill
- switchboardSkill
- tq-forge-agentSkill
- tq-forge-agentsSkill
- tq-forge-improve-allSkill
- tq-forge-improveSkill
- tq-forge-learnSkill
- tq-forge-listSkill
- tq-forge-queueSkill
- tq-forge-resumeSkill
- tq-forge-scanSkill
- tq-forgeSkill
- tq-forge-skillSkill
- tq-forge-statusSkill
- tq-forge-testSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Check the halt flag: If $TQ_FORGE_HOME/halt.flag exists, queue and exit:
- Distinctive: line 43
If neither exists, abort and list what's available:
- Distinctive: line 48
Re-score before promoting: Never trust a stale score:
- Very specific: line 53
If avg < 7 OR dry-test verdict != pass, refuse: "Score is X/10 — run /tq-forge-improve <slug> first."
- Very specific: line 77
Use cp -r, not mv — keep the sandbox copy as a rollback.
≈ “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
/tq-forge-promote — sandbox -> production
When to use
A skill or agent in $TQ_FORGE_HOME/sandbox/forged-{skills,agents}/<slug>/ has
passed scoring (>=7) and is ready to ship. This is the only path that writes
into $CLAUDE_SKILLS_DIR (default ~/.claude/skills).
Procedure
export TQ_FORGE_HOME="${TQ_FORGE_HOME:-$HOME/.tq-forge}"
S="${CLAUDE_PLUGIN_ROOT:-${TQ_FORGE_HOME:-$HOME/.tq-forge}/install}/scripts"
source "$S/common.sh" && tq_ensure_home- Check the halt flag. If
$TQ_FORGE_HOME/halt.flagexists, queue and exit:test -f "$TQ_FORGE_HOME/halt.flag" && bash "$S/forge-checkpoint.sh" queue "promote <slug>" && exit 0 - Resolve the slug.
If neither exists, abort and list what's available:for d in "$SANDBOX_SKILLS/<slug>" "$SANDBOX_AGENTS/<slug>"; do test -e "$d" && echo "FOUND: $d" donels "$SANDBOX_SKILLS" "$SANDBOX_AGENTS" - Re-score before promoting. Never trust a stale score:
If avg < 7 OR dry-test verdict !=bash "$S/quality-score.sh" --auto-detect "<slug>" bash "$S/dry-test.sh" "$SANDBOX_SKILLS/<slug>" # or $SANDBOX_AGENTSpass, refuse: "Score is X/10 — run /tq-forge-improve<slug>first." - Copy into production.
# Skill mkdir -p "$CLAUDE_SKILLS_DIR" cp -r "$SANDBOX_SKILLS/<slug>" "$CLAUDE_SKILLS_DIR/<slug>" # Agent mkdir -p "$CLAUDE_SKILLS_DIR/agents" cp -r "$SANDBOX_AGENTS/<slug>" "$CLAUDE_SKILLS_DIR/agents/<slug>" - Update skill-log.json status.
python3 -c "import json,pathlib,os;p=pathlib.Path(os.environ['TQ_FORGE_HOME'])/'skill-log.json';d=json.loads(p.read_text() or '[]');[e.update({'status':'promoted'}) for e in d if e.get('slug')=='<slug>'];p.write_text(json.dumps(d,indent=2))" - Print summary. slug, kind, final score, production path, and the reminder: "Restart Claude Code (or reload skills) to pick it up."
Pitfalls
- Use
cp -r, notmv— keep the sandbox copy as a rollback. Only delete the sandbox dir after the user confirms production works. - A slug already present at
$CLAUDE_SKILLS_DIR/<slug>/means a name collision with another skill set — refuse and ask the user to rename. - Skills are loaded at session start; a freshly promoted skill won't be callable until the session reloads. Say so explicitly.
Verification
$CLAUDE_SKILLS_DIR/<slug>/SKILL.md(oragents/<slug>/AGENT.md) exists.skill-log.jsonshowsstatus: promotedfor the slug.- Re-running quality-score on the production path still reports >=7.
Tags
tq-forge promote production
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.

