This repository starts as a template for building a skill repository.
- Open the template repository on GitHub.
- Click
Use this template. - Select
Create a new repository. - Choose the owner, repository name, description, and visibility.
- Click
Create repository from template. - Clone the generated repository.
- Add source material or a short skill idea to
.intake/. - Ask an AI coding agent to build the skill from intake.
- Let the agent assess and resolve intake gaps before skill construction.
- Let the agent rewrite the repository into maintenance mode.
- Review the generated skill, docs, manifests, and validation results.
The agent should not merely fill placeholders. It should infer the reusable capability hidden in the intake, decide what belongs in the skill, record important assumptions, and explain the reasoning that future maintainers need.
If the agent finds contradictions in the intake, it should resolve low-risk issues locally and document high-impact assumptions. The goal is a maintainable skill, not a perfect transcript of every source file.
If .intake/ is empty, weak, conflicting, or exploratory, the agent should not replace the placeholder skill immediately. It should first determine what is missing, why the missing evidence matters, and how to resolve the gap with minimal human help.
Expected resolution paths include extracting evidence, making low-risk assumptions, inspecting local tools or docs, creating disposable experiments, narrowing scope, asking concise questions, or stopping before construction when the skill would otherwise be fabricated.
The agent renames skills/placeholder-skill/ to the confirmed final name and builds its SKILL.md, runtime references, root installation guide, GitHub CLI orientation, separate maintenance fixtures, packaging manifests, release notes, and maintenance mode AGENTS.md.
After cleanup, .template/ should be gone. The repository should read like a normal skill repository, not a generated project.
The generated AGENTS.md should explain how to maintain the skill and why important boundaries exist. Future agents should not need to know this template existed.
BOOTSTRAP-WORKFLOW.md- Full lifecycle and cleanup rationale.ARCHITECTURE.md- Repository modes and authority model.