tq-forge-improve
Skill8 starsChanged 5 months agoMITView on GitHub
Re-score a forged skill or agent, identify weak dimensions, rewrite only those sections, then verify the score improved to >=7. One targeted pass; if still <7 after the rewrite, flags it for manual review. Use when asked for "/tq-forge-improve", "improve a skill", "fix a weak skill", or "this skill scored low".
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-learnSkill
- tq-forge-listSkill
- tq-forge-promoteSkill
- 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
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 40
Read the current content: Read the SKILL.md (or AGENT.md + system-prompt.md) at the path assess printed.
- Very specific: line 55
Use Edit for targeted swaps.
- Distinctive: line 74
Only rewrite weak sections.
≈ “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-improve — targeted rewrite of low-scoring sections
When to use
A forged skill or agent scored <7 and you want to fix it without rewriting the
whole artifact. Give it a slug (e.g. notion-daily-summary) or an absolute
path; the skill identifies which dimensions are pulling the score down,
rewrites only those sections, then verifies.
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- Assess the artifact.
This prints per-dimension scores, highlights weak dims (<7), and gives a coaching hint for each. Capture which sections need work.bash "$S/improve-loop.sh" assess "<slug>" - Read the current content. Read the SKILL.md (or AGENT.md +
system-prompt.md) at the path
assessprinted. Understand what each weak section currently says. Rewrite only the weak sections:
Dimension Section to rewrite clarity## When to use— <=3 sentences, concrete triggeractionability## Procedure— add copy-pasteable commandscompletenessAdd missing section(s): Pitfalls / Verification / Tags specificityReplace vague language with real paths / tool names consistencyDefine the output-format schema once, up top (agents) handoff_clarityhand_off_tointools.json— add awhen:per entryUse
Editfor targeted swaps; useWriteonly if the file is malformed. Preserve every section you are NOT rewriting, verbatim.- Verify the improvement.
This re-scores, prints before/after, and updatesbash "$S/improve-loop.sh" verify "<slug>"skill-log.json. - Branch on the result.
- avg >=7: print
✅ <slug> now scores X/10. Ready to promote.Suggest/tq-forge-promote <slug>if it's still in the sandbox. - avg <7: print the remaining weak dims and flag it:
bash "$S/forge-checkpoint.sh" review "<slug>" "<weak-dim>" "<score>"
- avg >=7: print
Pitfalls
- Only rewrite weak sections. Editing a strong section risks dropping its score while raising the weak one. Target precisely.
assessauto-detects sandbox and production paths. If the slug exists in both, it prefers the sandbox copy — improve there, then re-promote.- Agents have 6 scoring dimensions vs 4 for skills;
handoff_clarityandconsistencyapply only to agents. - Adding copy-pasteable bash commands often raises
actionability2-3 points on its own — try that before broader rewrites.
Verification
improve-loop.sh verify <slug>reportspassed: truein--jsonmode.skill-log.jsonshows the updatedscoreand alast_testedtimestamp.- The before score < 7 and the after score >= 7 (delta printed).
Tags
tq-forge improve quality rewrite single-slug
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.

