tlamatini-new-acp-agent

Scaffold end-to-end ACP agents with an eight-artifact contract for Tlamatini.

14|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-new-acp-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tlamatini-new-acp-agent
Source: https://github.com/XAIHT/Tlamatini/tree/main/Tlamatini/agent/skills_pkg/tlamatini_new_acp_agent
Command: npx skills add https://github.com/XAIHT/Tlamatini --skill tlamatini-new-acp-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold an end-to-end ACP agent scaffold for Tlamatini, reducing setup time and ensuring a consistent eight-artifact contract across script, config, views, migrations, CSS, JS, and docs.

Core Features & Use Cases

  • End-to-end ACP agent scaffolding: creates a new agent skeleton with script, config.yaml, Django view + URL, migration, CSS gradient, four JS files, agentic_skill.md, README.md, and lint setup.
  • Enforces a standard contract: validates agent_name and category input, updates multiple files, and prepares linting tasks.
  • Use Case: A developer wants to bootstrap a new agent named "my_acp_agent" in a chosen category with all boilerplate ready for customization.

Quick Start

Create a new ACP agent using the scaffold workflow.

Frequently Asked Questions about tlamatini-new-acp-agent

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

FAQPage Schema
How do I scaffold an ACP agent with Django views and migrations?

Scaffold an ACP agent by providing an agent_name and category to generate a complete skeleton including Django views, URLs, migrations, CSS, and JS boilerplate files.

What files are generated when bootstrapping a new agent?

Bootstrapping a new agent generates eight artifacts: script, config.yaml, Django view, URL, migration, CSS gradient, four JS files, agentic_skill.md, README.md, and lint setup.

Does the agent scaffolding process validate input parameters?

Yes, the scaffolding process validates input for agent_name and category, returning files_changed, migration_id, and lint_summary to ensure a standard agent contract.

What is the best way to standardize agent repository structure across teams?

Standardize agent repository structure by using an end-to-end scaffold that enforces a consistent eight-artifact contract across script, config, views, migrations, CSS, JS, and docs.

Can I use this scaffold to rapidly onboard new agents into a Tlamatini workflow?

Yes, you can rapidly onboard new agents into a Tlamatini workflow by generating the full boilerplate skeleton ready for immediate customization.