agents-onboarding
Skill4 starsChanged 10 months agoMITView on GitHub
Use when user integrates agents into repository, asks to set up agent guidance/rules/onboarding, or repo missing agent-specific onboarding docs (AGENTS.md). Ensures fresh agent context can apply all repo standards and external skills.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ktaroabobon/agent-skillstheir own version, first seen Aug 22, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ktaroabobon/agent-skills★ 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 repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-workitem-automationSkill
- architecture-testingSkill
- aspire-integration-testingSkill
- automated-standards-enforcementSkill
- best-practice-introductionSkill
- branching-strategy-and-conventionsSkill
- broken-windowSkill
- change-risk-rollbackSkill
- ci-cd-conformanceSkill
- component-boundary-ownershipSkill
- contract-consistency-validationSkill
- csharp-best-practicesSkill
- deployment-provenanceSkill
- documentation-as-codeSkill
- documentation-scaffoldSkill
- dotnet-bespoke-code-minimisationSkill
- dotnet-best-practicesSkill
- dotnet-domain-primitivesSkill
- dotnet-efcore-practicesSkill
- dotnet-healthchecksSkill
- dotnet-logging-serilogSkill
- dotnet-mapping-standardSkill
- dotnet-open-source-first-governanceSkill
- dotnet-source-generation-firstSkill
- dotnet-specification-patternSkill
- dotnet-testing-assertionsSkill
- environment-traceabilitySkill
- finishing-a-development-branch-iddSkill
- greenfield-baselineSkill
- impacted-scope-enforcementSkill
- incremental-change-impactSkill
- incremental-deploymentSkill
- innersource-governance-bootstrapSkill
- issue-driven-deliverySkill
- library-extraction-stabilisationSkill
- local-dev-experienceSkill
- markdown-authorSkill
- modern-csharp-coding-standardsSkill
- monorepo-orchestration-setupSkill
- observability-logging-baselineSkill
- pair-programmingSkill
- persona-switchingSkill
- process-skill-routerSkill
- quality-gate-enforcementSkill
- release-tagging-planSkill
- repo-best-practices-bootstrapSkill
- repository-foundation-bootstrapSkill
- requirements-gatheringSkill
- runtime-tooling-validationSkill
- safe-brownfield-refactorSkill
- scoped-colocationSkill
- security-processesSkill
- selective-build-testSkill
- semantic-version-impactSkill
- session-awareSkill
- skills-first-workflowSkill
- static-analysis-securitySkill
- structured-review-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Create AGENTS.md at repository root to enable fresh agent context to apply all repository standards and external skills.
- Distinctive: line 53
All of these mean: Apply skill, create comprehensive AGENTS.md.
≈ “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
Agents-Onboarding
Overview
Create AGENTS.md at repository root to enable fresh agent context to apply all repository standards and external skills. Fresh agents (no conversation history) must understand how to work in the repository by reading only AGENTS.md.
REQUIRED SUB-SKILL: superpowers:brainstorming
REQUIRED SUB-SKILL: superpowers:verification-before-completion
When to Use
- User integrates AI agents into repository for first time
- User asks to set up agent guidance, rules, or onboarding documentation
- Repository is missing agent-specific onboarding docs (no AGENTS.md)
- Fresh agent context needs to understand repository standards without conversation history
- Existing AGENTS.md is incomplete or outdated and needs enhancement
Core Workflow
- Announce skill and why it applies.
- Analyze repository for existing standards (brownfield) or define new (greenfield).
- Create AGENTS.md at repository root with required sections.
- Validate fresh context test: agent with only AGENTS.md can apply standards.
- Commit with evidence.
AGENTS.md Required Sections
- Repository Overview: Purpose, architecture, key constraints
- Required Skills: External (
superpowers:*) and custom skills with triggers - Development Standards: Code style, testing, review, deployment
- Repository Conventions: Directory structure, naming, documentation
- Process Guidance: PR workflow, deployment, escalation paths
- Context Optimization: What agents must know, focus areas
Red Flags - STOP
- "Agent can figure it out"
- "We'll document standards later"
- "Just need basic agent help"
- "Only one person uses agents here"
All of these mean: Apply skill, create comprehensive AGENTS.md.
References
references/AGENTS-TEMPLATE.md- Complete template with annotationsreferences/standards-discovery.md- Repository analysis techniquesreferences/rationalizations.md- Excuses and reality checks
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.

