tech-debt
Skill0 starsChanged 8 months agoNo licenceView on GitHub
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
36 other projects use a version of this, 1 of them edited.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- y-miyazaki/configtheir own version, first seen Nov 6, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- dpleshakov/tfsclitheir own version, first seen Oct 20, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Oct 19, 2026
Used with
Projects with it also use playtest-report, soak-test and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
- lilangMaxSkill
team-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
- CoralGameSkill
team-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
Also in 14 projects that use this
- +5 more from lilangMax
- +3 more from CoralGame
Other versions36 projects use a version of this.
Word for word · 2
- anthropics/knowledge-work-plugins★ 35k100% same
- edu6565/claude-skills★ 0100% same
Edited · 1
- InfiniteRoomLabs/agent-ops★ 093% same
Wrote their own version · 33
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- vm0-ai/vm0★ 1.2ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 118same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- drafthq/draft★ 40same name
- fagemx/edda★ 36same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dirien/yet-another-agent-harness★ 19same name
23 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- dec-data-specialistSkill
- deconetwork-catalogue-importSkill
- accessibility-reviewSkill
- architectureSkill
- code-reviewSkill
- context7-mcpSkill
- debugSkill
- deploy-checklistSkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- documentationSkill
- frontend-designSkill
- dev-fullstackSkill
- incident-responseSkill
- research-synthesisSkill
- standupSkill
- system-designSkill
- testing-strategySkill
- user-researchSkill
- ux-copySkill
- fin-finance-managerSkill
- fin-xero-invoice-pipelineSkill
- max-marketingSkill
- brand-reviewSkill
- campaign-planSkill
- competitive-briefSkill
- content-creationSkill
- draft-contentSkill
- email-sequenceSkill
- performance-reportSkill
- seo-auditSkill
- account-researchSkill
- call-prepSkill
- call-summarySkill
- competitive-intelligenceSkill
- create-an-assetSkill
- daily-briefingSkill
- draft-outreachSkill
- forecastSkill
- pipeline-reviewSkill
- sara-email-projectsSkill
- brainstormingSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
The file
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.