context-guardian
Skill3 starsChanged 35 days agoApache-2.0View on GitHub
Define one task owner, output, scope, and acceptance criteria. Use for context guardian tasks.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- CareoLimited/context-guardiantheir own version, first seen Nov 15, 2026
- usibuilds/claude-context-zonestheir own version, first seen Nov 8, 2026
- charly-vibes/incitacionestheir own version, first seen Oct 14, 2026
- brunoflma/context-guardiantheir own version, first seen Jul 5, 2026
- Fandry96/k3-agentic-skillstheir own version, first seen May 12, 2026
- xiangu152/my_claude_skillstheir own version, first seen Apr 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Fandry96/k3-agentic-skills★ 27same name
- brunoflma/context-guardian★ 3same name
- xiangu152/my_claude_skills★ 2same name
- CareoLimited/context-guardian★ 0same name
- charly-vibes/incitaciones★ 0same name
- usibuilds/claude-context-zones★ 0same name
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 repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- admin-hr-legal-officerSkill
- ai-voice-audio-engineerSkill
- automation-ops-engineerSkill
- b2b-sales-hunterSkill
- brand-identity-engineerSkill
- business-analyst-discoverySkill
- client-success-guardianSkill
- competitor-spy-analystSkill
- creative-directorSkill
- creative-frontend-designerSkill
- data-harvesterSkill
- deal-closerSkill
- delivery-directorSkill
- distributed-systems-architectSkill
- executive-accountantSkill
- frontend-ux-auditorSkill
- fullstack-mvp-engineerSkill
- funnel-cro-auditorSkill
- graphic-design-producerSkill
- growth-director-orchestratorSkill
- legacy-code-rescue-specialistSkill
- machine-control-operatorSkill
- mcp-integration-builderSkill
- network-infra-engineerSkill
- paid-media-buyerSkill
- qa-test-automation-engineerSkill
- reverse-engineering-analystSkill
- rfp-proposal-engineerSkill
- security-operations-guardianSkill
- seo-growth-engineerSkill
- short-form-paid-boosterSkill
- skill-forge-recruiterSkill
- skill-improvement-engineerSkill
- skill-performance-auditorSkill
- studio-directorSkill
- tech-stack-architectSkill
- toolbox-integration-stewardSkill
- trend-hunter-ideatorSkill
- ultra-light-optimizerSkill
- video-assembly-editorSkill
- video-script-architectSkill
- viral-hook-architectSkill
- visual-qa-reviewerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this role for context guardian work.
- Very specific: line 14
Read the workspace constitution and the five files in brain/ before execution.
- Distinctive: line 20
Use complete sources or explicit read references.
- Distinctive: line 29
Update completed work, challenges, ideas, and backlog with concise records.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context Guardian
When to use
Use this role for context guardian work. Match the task scope before activation; do not assume the host has external tools or account permissions.
Brain and preflight
Read the workspace constitution and the five files in brain/ before execution. Confirm the requested output language, input facts, authority, dependencies, and acceptance criteria.
Procedure
- Define one task owner, output, scope, and acceptance criteria.
- Build a bounded context pack from the chosen skill and relevant memory.
- Use complete sources or explicit read references; never silently truncate requirements.
- Track failure signatures and previous attempts across handoffs, then verify and sync memory.
Deliverable and verification
Deliver the concrete artifact or findings, the evidence used, checks performed, and remaining limitations. Use Arabic or English as requested. Identify missing tools or facts explicitly; do not fill gaps with invented results.
Closure
Update completed work, challenges, ideas, and backlog with concise records. Keep credentials and private customer records out of shared memory.
Detailed procedures and specialist references
Read the English procedure for project execution. Read the full Arabic playbook for role boundaries, step-by-step procedures, acceptance conditions, and handoff requirements. Read the specialist architecture when selecting tools and project inputs. The English entry point and shared constitution govern public task execution. Source-specific external documents are project inputs, not bundled private records.
Included executable tools
- context: Bounded English or Arabic context pack.
See the tool catalog for commands, inputs, side effects and exit behavior.
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.

