Install
$ agentstack add skill-sharpdeveye-maestro-onboard-agent ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
Bootstrap a new agent workflow from scratch, or add a new agent to an existing system.
Step 1: Establish Conventions
## Workflow Conventions
### Prompt Format
- Delimiter style: [XML tags / markdown headers / triple-dash]
- Section order: [System → Context → Instructions → Input]
- Output format: [JSON with schema / markdown template]
### Tool Conventions
- Naming: [verb_noun / noun.verb / camelCase]
- Description template: [What → When → When Not → Returns]
- Error format: [{ code, message, details }]
### Logging
- Format: [JSON structured]
- Required fields: [workflow_id, step, timestamp, level]
### File Structure
- Prompts: [prompts/workflow-name/v1.md]
- Tools: [tools/tool-name.{ext}]
- Config: [config/environment.yaml]
- Tests: [tests/workflow-name/]
Step 2: Create Initial Structure
project/
├── prompts/ # System prompts, versioned
├── tools/ # Tool definitions
├── config/ # Environment-specific configuration
├── tests/ # Golden test sets and evaluation suites
├── logs/ # Runtime logs (gitignored)
└── .maestro.md # Workflow context
Step 3: Create the First Agent
- System prompt: Role definition with constraints
- 2-3 essential tools: Start with the minimum viable tool set
- Output schema: Define expected output format
- One golden test: At least one test case with known-good output
- Basic error handling: Structured error responses
- Logging: Structured log output for each run
Step 4: Verify
- Run the agent with the golden test case
- Verify error handling works (send bad input)
- Verify logging captures useful context
Recommended Next Step
After onboarding, run /diagnose for a baseline health check, then /fortify to add production-grade error handling.
NEVER:
- Start building without establishing conventions
- Create tools without descriptions
- Skip the golden test case
- Over-scope the initial agent (start minimal, amplify later)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sharpdeveye
- Source: sharpdeveye/maestro
- License: MIT
- Homepage: https://maestroskills.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.