onboarding-index
SolidDiscover CEP-managed content already present in a target repo (What/How layer docs, compiled guidelines, context packages, decision ledger) via existence checks against layout-slots-registry.yaml-resolved paths, then write one canonical root AGENTS.md onboarding index plus thin per-tool pointer stubs (.github/copilot-instructions.md, CLAUDE.md, .cursor/rules/onboarding.mdc) that link into it. All writes are marked-block or existence-gated and non-destructive, including install.sh's own AGENTS.md skill-catalog block. Codex needs no separate stub -- root AGENTS.md is already its native onboarding format. Do NOT use it to generate the CEP content itself (ult-autoscaffold-content/compiling-project-guidelines do that) or to resolve layer paths (ult-repo-layout does that). Do NOT confuse it with this OSS repo's own AGENTS.md (generated by catalog/export_adapters.py) -- this skill only ever writes into a separate target repo being onboarded with CEP.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- linkpranay-ai
- Repository
- linkpranay-ai/context-engineering-protocol
- Created
- 2 months ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
autoscaffold-content
Generate real starter content for a project's What-L2 (requirements) and How-L2 (architecture/conventions) CEP layers once ult-repo-layout has resolved their paths but found them empty — an honest, minimal, YAML-frontmatter-first overview document per layer for small/single targets, or graphify-informed per-module tiering with resumable per-module CONTEXT.md generation, existence-gated CODING-STANDARDS.md/TESTING-GUIDELINES.md, interface-boundary docs for graph-crossing module pairs, and a rendered CEP-INDEX.md router for large repos, optionally informed by a user-supplied domain-pack of terminology/references if one is configured. This skill generates a NEW starter doc only when none exists — it never compiles or reconciles EXISTING scattered guideline sources (that's compiling-project-guidelines' job). Do NOT use to enforce layout paths or run layer discovery — that's ult-repo-layout. Do NOT use to author or generate a domain pack — this skill only ever consumes one you already wrote.
hr-onboard
Discovers what belongs in a repository's AGENTS.md by attempting real work and recording the friction, rather than by scanning the codebase and describing it. Use this whenever the user mentions AGENTS.md, CLAUDE.md, agent instructions, a context file, steering docs, onboarding a repo for agents, or asks what they should write down for their coding agent - and also when they ask why an agent keeps making the same mistake in this repo, or want to trim an instruction file that has grown too long. Use it even if they do not name a file, and even if they only say something like "set this project up for Claude" or "make Codex work properly here".
onboarding
Use when onboarding a repository for agentic development: preparing it so an outside developer, or an agent, can pick it up without asking questions. Works on an existing codebase or a brand new one. Trigger whenever the user asks to onboard a repo or project, make it agent-ready, prepare it for Claude, set up CLAUDE.md or AGENTS.md and the docs behind them, asks why agents struggle to work in this codebase, or is starting a new project and wants it set up right from the first commit, even if they never say the word onboarding.