agentsclimarketplace

Create agent

Skill theinterneti/TTA.dev/.github/skills/create-agent

AI devops for vibe coders

Install
npx -y skills add theinterneti/TTA.dev --skill create-agent

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when creating, modifying, or debugging a custom Copilot agent (.agent.md file). Provides detailed patterns for agent orchestration, handoffs, sub-agent invocation, tool configuration, variable extraction, and prompt structure. Invoke when the user says "create an agent", "add a new agent", "agent handoffs", "sub-agent", or "orchestrate agents".

SKILL.md

1.7 KB, as published. Nobody here has run it

Create Agent

Detailed reference for building custom Copilot agents in TTA.dev. For atomic rules (naming, frontmatter, registration), see the agents instruction.

When to Use This Skill

  • Creating a new .agent.md file from scratch
  • Adding handoffs between agents for workflow transitions
  • Setting up sub-agent orchestration (multi-step pipelines)
  • Configuring tool access and MCP server integration
  • Designing agent prompt structure with dynamic variables

Prerequisites

  • Understand the composition model
  • Know which skills and workflows your agent needs (check .github/copilot-catalog.yml)
  • Have the target agent's role and responsibilities defined

Quick Start

  1. Create .github/agents/my-agent.agent.md with frontmatter
  2. Write the body following the Role → Responsibilities → Constraints pattern
  3. Add entry to .github/copilot-catalog.yml with skill_refs and workflow_refs
  4. Validate: uv run python scripts/validate-catalog.py

Reference Docs

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.