tkarakai/ai-agent-instruction-templates

Overview

This skill loads an AI agent instruction template into the current project's .agents/ directory to give you a ready-made set of role-specific instructions. It automates downloading, placing agent instructions, recording version metadata, and pulling any declared dependencies. Use it to quickly add structured agent roles such as technical planners without manual setup.

How this skill works

You invoke the loader with the template name (and optional version). The loader script downloads the template from the remote repository, creates .agents/<template-name>/AGENTS.md containing the agent instructions, and writes version and provenance into .agents/.loaded-templates.yaml. If the template declares dependencies, the loader recursively pulls and installs them into .agents/.

When to use it

• You need a vetted instruction set for a specific agent role (e.g., technical planner).
• Setting up a project with repeatable, shareable agent roles and workflows.
• Onboarding new team members who will run agents and need clear instructions.
• Preparing commit or PR metadata that links which templates were used.
• When you want to reuse community or organization templates with version traceability.

Best practices

• Keep .agents/ in .gitignore to avoid committing generated or private instruction files.
• Specify a version (e.g., @v1.0.0) to ensure reproducible agent behavior.
• Open and review .agents/<template-name>/AGENTS.md before running agents to confirm required inputs.
• Commit .agents/.loaded-templates.yaml when the template is authoritative for the project’s workflow.
• Use /list-templates first to preview available templates and avoid unnecessary downloads.

Example use cases

• Load a Software-Technical-Planner template to generate a step-by-step technical planning agent for project design.
• Bootstrapping QA or review agents across multiple repositories using the same instruction standard.
• Onboarding: add instruction templates so new contributors run consistent agent-driven tasks.
• Auditability: record which template versions were used for later reproducibility and PR notes.