skills
CLAUDE.md1 starsChanged 58 days agoBSD-2-ClauseView on GitHub
@.github/copilot-instructions.md
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- code-tidySkill
- curate-releaseSkill
- customer-strategy-forgeSkill
- designing-for-intentSkill
- feature-to-planSkill
- go-testable-designSkill
- instruction-styleSkill
- issue-refine-loopSkill
- mutation-hunterSkill
- optimize-prompt-loopSkill
- plan-to-graphSkill
- rugged-evil-testerSkill
- skill-reviewerSkill
- spec-auditorSkill
- to-earsSkill
- triaging-pr-reviewsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
When updating project conventions, pull request requirements, or core mandates, you MUST apply those changes to …
- Very specific: line 13
Follow the guidelines in the imported instructions for evaluating and linting your work using MCP tools and the skill-reviewer skill.
- Very specific: line 17
Run the lint suite via the Bash tool: npx -y @lousy-agents/cli lint.
- Very specific: line 19
Use the lousy-agents MCP server tools directly when you need fine-grained signals: mcp__lousy-agents__analyze_instruction_quality, …
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
Lousy Agents Skills — Claude Code Context
⚠️ Source of Truth
The foundational mandates, core philosophy, and strict negative constraints for this repository are managed centrally and imported below.
@.github/copilot-instructions.md
Agentic Parity Mandate
When updating project conventions, pull request requirements, or core mandates, you MUST apply those changes to .github/copilot-instructions.md rather than this file. This file should only contain Claude-specific operational instructions.
Claude Workflow Instructions
- Utilize the
.claude/settings.local.jsonfile for any local Claude configurations as needed. - Follow the guidelines in the imported instructions for evaluating and linting your work using MCP tools and the
skill-reviewerskill.
Commands
Claude-specific tool surfaces for the canonical commands documented in .github/copilot-instructions.md:
- Run the lint suite via the
Bashtool:npx -y @lousy-agents/cli lint. - Invoke the
skill-reviewerskill via theSkilltool (it is listed in the available-skills surface). - Use the
lousy-agentsMCP server tools directly when you need fine-grained signals:mcp__lousy-agents__analyze_instruction_quality,mcp__lousy-agents__validate_instruction_coverage,mcp__lousy-agents__analyze_action_versions, etc.
Validation
Imported from .github/copilot-instructions.md.
Verification
Imported from .github/copilot-instructions.md.
Feedback Loop
Imported from .github/copilot-instructions.md.
Mandatory
Imported from .github/copilot-instructions.md.
Before Commit
Imported from .github/copilot-instructions.md.
Validation Suite
Imported from .github/copilot-instructions.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.

