create agent

AI Community

Skill notes

STEP 1: Gather Agent Requirements

If the user provided a topic as an argument, use it as context. Otherwise, ask. Use AskUserQuestion to gather the following (can be a single open-ended question if user already provided detail, or multiple focused questions):

1a. Agent Purpose

Question: "What should this agent do? Describe its purpose, who it serves, and what problems it solves." Header: "Agent Purpose" Get enough detail to write a meaningful CLAUDE.md. Push for specifics — not "a coding agent" but "an agent that reviews Python PRs for a data engineering team and checks for SQL injection, missing tests, and schema migration issues."

1b. Agent Name

Question: "What should the agent be called?" Header: "Agent Name" Suggest a name based on the purpose (lowercase-with-hyphens, short, memorable) Let the user override This becomes the directory name and the agent identity

1c. Destination

Question: "Where should I create the agent?" Header: "Location" Options: ~/[agent-name] — Home directory (recommended) ./[agent-name] — Current directory

1d. Initial Skills

Question: "What should this agent be able to do from day one? List 2-4 key capabilities." Header: "Starting Skills" Examples based on the purpose — if it's a content agent, suggest: "generate blog posts, review drafts, manage editorial calendar." If it's an ops agent: "check service health, deploy updates, investigate incidents." These will become the agent's first skills.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Required · Vendor-specific
Operating systems
macOS · Linux · Windows
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview create-agent.preview
# 7a. Create .env.example

# [Agent Display Name] Configuration
# Copy this to .env and fill in your values

# Trinity Platform Connection (optional — for remote deployment)
# Get your API key from your Trinity dashboard > Settings > API Keys
TRINITY_URL=https://your-trinity-instance.example.com
TRINITY_API_KEY=your-api-key-here

[AGENT_SPECIFIC_VARS]

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.