agents-bootstrap-sync

Generate AGENTS.md and configuration files from documentation templates.

1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill agents-bootstrap-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-bootstrap-sync
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/agents-bootstrap-sync
Command: npx skills add https://github.com/hadenlabs/tasks --skill agents-bootstrap-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap agent configuration and generate AGENTS.md from docs using a template-based, idempotent approach without external templating engines.

Core Features & Use Cases

  • Bootstrap jasper.toml and .goji.json
  • Generate AGENTS.md as an entrypoint for agents
  • Idempotent and safe operation

Quick Start

Use the agents-bootstrap-sync skill to bootstrap agent configuration and generate AGENTS.md from docs.

Frequently Asked Questions about agents-bootstrap-sync

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

FAQPage Schema
How do I generate AGENTS.md from existing documentation sources?

You can generate AGENTS.md by using a template-based, idempotent approach that renders documentation sources alongside AGENTS.md.tpl, jasper.toml.tpl, and .goji.json.tpl templates without external templating engines.

What is idempotent agent bootstrap and how does it keep configuration safe?

Idempotent agent bootstrap applies a template-based approach to generate jasper.toml and .goji.json safely, ensuring repeated operations produce the same configuration without side effects or data loss.

Do I need external templating engines to bootstrap agent configuration files?

No, you do not need external templating engines to bootstrap agent configuration. The process renders jasper.toml, .goji.json, and AGENTS.md directly from provided templates without external dependencies.

What directory structure is required to bootstrap jasper.toml and .goji.json?

Bootstrapping jasper.toml and .goji.json requires a docs directory containing the necessary AGENTS templates (jasper.toml.tpl, .goji.json.tpl, AGENTS.md.tpl) to render the configuration files and entrypoint.

Why should I use a template-based approach for centralized agent documentation?

A template-based approach ensures idempotent, safe operation across deployments by generating a consistent AGENTS.md entrypoint from documentation sources without relying on external templating engines.