init-agent

Resolve agent placeholders and condition blocks in shared coding rule templates.

Updated Aug 14, 2025
One-click install
npx skills add https://github.com/kaikojima05/ai-agent-rules --skill init-agent-kaikojima05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-agent
Source: https://github.com/kaikojima05/ai-agent-rules/tree/main/skills/init-agent
Command: npx skills add https://github.com/kaikojima05/ai-agent-rules --skill init-agent-kaikojima05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of adapting the same shared rules and skill templates to different AI coding agents by automating placeholder resolution and agent-specific condition handling.

Core Features & Use Cases

  • Agent-specific placeholder substitution: Rewrites [agent_name] across AGENTS.md-adjacent templates in skills/, hooks/, and rules/ based on the selected agent type.
  • Resolves [NOTE]: init-agent 対象 implementations: Converts note placeholders (including tool/condition logic) into the correct per-agent shell condition snippets.
  • Safety checks for template integrity: Excludes the skill’s own SKILL.md from placeholder replacement and supports verification of remaining unresolved placeholders via grep.

Quick Start

Tell your AI to run /init-agent claude to generate Claude-specific configuration content by replacing placeholders and resolving the init-agent target notes.

Frequently Asked Questions about init-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate AI agent configuration setup across multiple ecosystems?

Automate AI agent configuration setup by resolving `[agent_name]` placeholders and `[NOTE]: init-agent 対象` blocks across templates in `skills/`, `hooks/`, and `rules/` directories. This applies cross-agent templates when different ecosystems use varying directory names.

What is the best way to share coding rules across different AI coding agents?

Share coding rules by using a template provisioning approach that rewrites `[agent_name]` placeholders in AGENTS.md-adjacent templates. This converts note placeholders into correct per-agent shell condition snippets for the selected agent type.

Does agent setup configuration automation work without invoking the model?

Yes, agent setup configuration automation disables model invocation entirely. It requires only Read, Grep, Glob, and Shell tool support to resolve placeholders and apply agent-specific condition handling.

How do I verify unresolved placeholders after running cross-agent template provisioning?

Verify unresolved placeholders after template provisioning by using grep to scan the generated configuration files. The automation reports resolved replacement values and supports post-run placeholder verification to ensure integrity.

Why does configuration automation exclude the source template SKILL.md from placeholder replacement?

Configuration automation excludes the source template `SKILL.md` from placeholder replacement as a safety check for template integrity. This prevents accidental modification of the original template structure during agent-specific substitution.

Can I use shell hooks for cross-agent rules when multiple agent ecosystems have different config directory names?

Yes, you can use shell hooks for cross-agent rules when ecosystems use different config directory names. The automation resolves `[NOTE]: init-agent 対象` implementations into correct per-agent shell condition snippets to handle these variations.