gym-project-maintainer
Coordinates development tasks, documentation, and reporting for the gym management system.
Install
mkdir -p .claude/skills/gym-project-maintainer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12920" && unzip -o skill.zip -d .claude/skills/gym-project-maintainer && rm skill.zipInstalls to .claude/skills/gym-project-maintainer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Maintain cross-surface docs, report material, chat context, and backend memory boundaries for this gym management system. Use when Codex must coordinate more than one gym documentation/context surface or decide which project material to load; use the phase-specific gym skills for focused plan, implement, review, test, completion, docs, or report work.Key capabilities
- →Read `docs/README.md` and `CHAT_CONTEXT/README.md`
- →Load only source and context files required by the active task
- →Update `docs/api_contract.md` and `api_test.http` when HTTP behavior changes
- →Update `docs/README.md` when a new durable document becomes an entrypoint
- →Keep `CHAT_CONTEXT/README.md` short for resuming new chats
- →Reconcile planned report text with code and `docs/api_contract.md`
How it works
The skill maintains cross-surface documentation, report material, and chat context for a gym management system by coordinating information flow and routing tasks to specific phase-specific skills.
Inputs & outputs
When to use gym-project-maintainer
- →Updating api contracts
- →Preparing system reports
- →Managing project documentation
About this skill
Gym Project Maintainer
Start
- Read
docs/README.md. - Read
CHAT_CONTEXT/README.md. - Read only the source and context files required by the active task.
Choose The Lane
Use the focused skill when one lane is clear:
| Task | Skill |
|---|---|
| Plan backend feature | $gym-plan |
| Implement backend feature | $gym-implement |
| Review backend feature | $gym-review |
| Test backend feature | $gym-test |
| Finalize feature docs/context | $gym-complete |
| Resume backend work | $gym-resume |
| Summarize backend status | $gym-status |
| Maintain durable docs | $gym-docs |
| Prepare report material | $gym-report |
| Git/GitHub and version control | $gym-git |
Documentation
- Keep durable project docs in
docs/. - Update
docs/api_contract.mdandapi_test.httpwhen HTTP behavior changes. - Check handlers, services, routes, and models before documenting exact behavior.
- Update
docs/README.mdwhen a new durable document becomes an entrypoint.
Report Material
- Keep report chapter inputs in
docs/report-materials/. - Reconcile planned report text with code and
docs/api_contract.mdbefore claiming a behavior is implemented. - Use
docs/system_analysis_design_guide.mdanddocs/faq_why.mdwhen report structure or rationale is needed.
Chat Context
- Keep
CHAT_CONTEXT/README.mdshort enough to resume a new chat. - Store status, decisions, risks, and next files to load. Do not paste code, secrets, long logs, or report drafts into chat context.
- Move durable explanations into
docs/and report drafts intodocs/report-materials/.
Backend Delivery
Use the backend phase skill that matches the active task. Those skills read references/backend-delivery.md for shared rules and feature memory layout.
Quality Rules
- Prefer one clear source of truth over duplicate summaries.
- Treat source code and route wiring as truth for implemented behavior, then align API docs and context summaries.
- Preserve report drafts when they represent target scope, but label planned behavior clearly.
- Keep context loading narrow; do not read every feature log for one task.
- Verify docs structure after moving files by searching for stale paths.
- Validate this skill after changing its metadata or bundled references.
When not to use it
- →Do not paste code, secrets, long logs, or report drafts into chat context
- →Do not read every feature log for one task
- →Do not use vague suggestions like 'consider reviewing'
Limitations
- →Prefer one clear source of truth over duplicate summaries
- →Treat source code and route wiring as truth for implemented behavior, then align API docs and context summaries
- →Keep context loading narrow; do not read every feature log for one task
How it compares
This workflow centralizes the management of diverse project materials and context, ensuring consistency and efficient task routing, unlike fragmented documentation and context handling.
Compared to similar skills
gym-project-maintainer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gym-project-maintainer (this skill) | 0 | 2mo | No flags | Intermediate |
| archon | 9 | 9mo | Review | Intermediate |
| linear | 10 | 2mo | No flags | Beginner |
| zapier-workflows | 11 | 8mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
archon
coleam00
Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
attio-skill-generator
kesslerio
Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.
github-manage
matteocervelli
Manage operations concerning GitHub on behalf of user
cto-engineering-metrics
rinaldofesta
Expert methodology for defining, tracking, and interpreting engineering performance metrics including DORA, team health, productivity, and executive reporting.