schemas

Data Community

Skill notes

Field Reference

Field · Required · Values · Description name · Yes · lowercase-with-hyphens · Agent identifier description · Yes · Multi-line string · 3-5 usage examples model · Yes · sonnet, opus, haiku · AI model to use color · No · See colors below · Terminal color

Color Guidelines

Color · Agent Type · Examples purple · Planning · architect, api-architect green · Implementation · developer, ui-developer cyan · Review · reviewer, designer orange · Testing · test-architect, tester

Tool Patterns by Agent Type

Orchestrators (Commands): Must have: Task, TodoWrite, Read, Bash Often: AskUserQuestion, Glob, Grep Never: Write, Edit Planners:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@majiayu000 · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

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

Output preview schemas.preview
# Missing Examples

# WRONG - too generic
description: Use this agent for development tasks.

# CORRECT
description: |
  Use this agent when implementing TypeScript features. Examples:
  (1) "Create a user service" - implements service with full CRUD
  (2) "Add validation" - adds Zod schemas to endpoints
  (3) "Fix type errors" - resolves TypeScript compilation issues

Discussion

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