agentleFS
thunderphonethunderphone/skills/create-agent/SKILL.md

create-agent

Skill0 starsChanged 57 days agoMITView on GitHub

Create, configure, update, deploy, or discard a ThunderPhone voice agent. Use when someone asks to build an agent, choose Spark versus Bolt versus Storm, select a language or voice, call POST /v1/agents, or understand draft and deployed revisions.

  • Reads credentials
  • Sends data out

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use deploy-platform, setup-platform and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • agno-agiSkill

    deploy-platform

    Deploy this AgentOS using its own provider instructions, configure JWT verification, and verify the public service. Use for first deployment, redeployment, or production configuration changes.

    Also in 5 projects that use this

  • agno-agiSkill

    setup-platform

    Set up this AgentOS from a fresh clone — confirm Docker, configure .env, boot the containers, prove the MCP endpoint live, connect the AgentOS UI, then build the user's first agent. Use when the user asks to set up the platform, get started, or bring this repo up on a new machine.

    Also in 5 projects that use this

  • ElasticSkill

    create-integration

    Use when creating a new Elastic integration package, scaffolding data streams, answering package layout or structure questions, or running the end-to-end integration build workflow. Covers package topology, scaffold commands, post-scaffold edits, and full orchestration of CEL/pipeline/test subagents.

    Also in 3 projects that use this

  • MicrosoftSkill

    create-hook

    Create a hook (.json) to enforce policy or automate agent lifecycle events.

    Also in 5 projects that use this

  • AnasX7Skill

    improve

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

    Also in 5 projects that use this

  • ElasticSkill

    create-skill

    Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.

    Also in 13 projects that use this

  • +3 more from agno-agi

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Select a tier: Use current prices from the pricing guide, not cached estimates.

    line 13
  2. Very specific:

    Resolve real options: Call GET /v1/voices and use its returned voice ID.

    line 24
  3. Very specific:

    Check the supported-languages guide before choosing language.

    line 25
  4. Distinctive:

    Use supported languages and the live voices endpoint.

    line 95
  5. Distinctive:

    Never fabricate IDs, credentials, voices, prices, or successful deployment evidence.

    line 96
  6. Distinctive:

    Treat deployment as a behavior change.

    line 97

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create a ThunderPhone agent

  1. Select a tier. Use current prices from the pricing guide, not cached estimates.
<!-- rate:tiers -->
Tierproduct valuesChoose it for
SparksparkStructured, narrow calls where cost is the priority.
BoltboltGeneral production calls that need stronger reasoning.
Stormstorm-base, storm-base-with-ack, storm-extra, storm-extra-with-ackComplex conversations and the highest capability.
<!-- /rate -->
  1. Resolve real options. Call GET /v1/voices and use its returned voice ID. Check the supported-languages guide before choosing language. Do not invent a voice ID, locale, or product string.
  2. Write the prompt with thunderphone-prompt-builder. Keep policy and facts general; do not script caller-response branches.
  3. Create the agent. name, prompt, and voice are required. The create response is deployed revision 1. Valid product values are listed in references/agent-fields.md.
{
  "name": "Dental receptionist",
  "prompt": "You are the receptionist for the dental practice. Help callers with scheduling and practice information. Use the caller's language when supported. Keep spoken responses concise.",
  "voice": "${VOICE_ID}",
  "product": "bolt",
  "primary_language": "en-US"
}
curl --fail-with-body -X POST https://api.thunderphone.com/v1/agents \
  -H "Authorization: Bearer $THUNDERPHONE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "X-ThunderPhone-Client: skills/create-agent@1.0" \
  --data-binary @agent.json
import os, requests

payload = {"name": "Dental receptionist", "prompt": os.environ["AGENT_PROMPT"],
           "voice": os.environ["VOICE_ID"], "product": "bolt", "primary_language": "en-US"}
r = requests.post("https://api.thunderphone.com/v1/agents", json=payload,
    headers={"Authorization": f"Bearer {os.environ['THUNDERPHONE_API_KEY']}",
             "X-ThunderPhone-Client": "skills/create-agent@1.0"}, timeout=30)
r.raise_for_status()
agent = r.json()
print(agent["id"])
const response = await fetch("https://api.thunderphone.com/v1/agents", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.THUNDERPHONE_API_KEY}`,
    "Content-Type": "application/json", "X-ThunderPhone-Client": "skills/create-agent@1.0" },
  body: JSON.stringify({ name: "Dental receptionist", prompt: process.env.AGENT_PROMPT,
    voice: process.env.VOICE_ID, product: "bolt", primary_language: "en-US" }),
});
if (!response.ok) throw new Error(await response.text());
console.log((await response.json()).id);
  1. Edit deliberately. PATCH /v1/agents/{agent_id} creates or updates a draft. Inspect it, then POST /v1/agents/{agent_id}/deploy. Use POST /v1/agents/{agent_id}/discard-draft to abandon unshipped changes.
  2. Verify. Fetch GET /v1/agents/{agent_id} and confirm the deployed and draft state matches the intended revision. Then run the test-agent skill.

Errors

SymptomCauseFix
400 with field errorsUnsupported product, language, voice, or malformed promptUse GET /v1/voices, the language guide, and the response's field errors.
403Organization lacks access or a policy gate appliesCheck organization access; do not downgrade around a stated gate silently.
Draft changes do not affect callsDraft was not deployedReview the draft, then call the deploy endpoint.
Existing behavior disappearedA full replacement omitted fieldsPrefer PATCH for scoped edits and reread the agent before deploying.

Source and safety rules

  • Confirm fields in the agents API reference.
  • Confirm tier rates in pricing.
  • Use supported languages and the live voices endpoint.
  • Never fabricate IDs, credentials, voices, prices, or successful deployment evidence.
  • Treat deployment as a behavior change; test the exact deployed revision.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.