create-new-agent

Scaffold a complete Tlamatini workflow agent contract with backend, config, views, migrations, UI assets, and linting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a canonical, end-to-end contract for scaffolding a NEW Tlamatini workflow agent, consolidating all required files and checks into a single, authoritative process.

Core Features & Use Cases

  • 8-step agent contract: backend script + config.yaml, Django view + URL, seed migration, CSS gradient, four JavaScript files, agentic_skill.md, README.md, and lint.
  • Standardization & guardrails: ensures consistent naming, surface area for FlowCreator, and integration with companion skills.
  • Usage: when creating a new agent, follow the canonical guide to reliably scaffold all artifacts and pass lint checks.

Quick Start

Read the canonical guide at Tlamatini/.agents/workflows/create_new_agent.md and follow the 8-step contract to scaffold a new agent.

Frequently Asked Questions about create-new-agent

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

FAQPage Schema
How do I scaffold a new workflow agent for Tlamatini end-to-end?

To scaffold a Tlamatini workflow agent, follow an 8-step contract to generate the backend script, config.yaml, Django view, URL routing, seed migration, CSS gradient, JavaScript files, README, and linting checks.

What files and configurations are required to create a Tlamatini agent?

Creating a Tlamatini agent requires generating a backend script, config.yaml, Django view and URL, seed migration, CSS gradient, four JavaScript files, agentic_skill.md, README.md, and passing lint checks.

Why do I need a standardized contract for backend agent scaffolding?

A standardized scaffolding contract ensures consistent naming, proper reanimation behavior, contract registry integration, and environment policies to safeguard production use across Python and JavaScript tooling.

Does agent scaffolding work with both Python and JavaScript tooling?

Yes, agent scaffolding enforces end-to-end operability across both Python and JavaScript tooling by generating required backend scripts, frontend UI assets, and enforcing lint checks.

What limitations or guardrails exist when generating agent config and views?

The scaffolding process enforces strict naming conventions, reanimation behavior, contract registry rules, and environment/temporary directory policies to prevent production issues and ensure FlowCreator compatibility.

Can I use this scaffolding process to generate Django views and seed migrations together?

Yes, the scaffolding process generates the Django view and URL alongside the seed migration as part of the complete 8-step contract to ensure full backend and database integration.