Skip to content
Back to skills

Onboard Agent

ASecurity

Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch.

  • 415 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aigogit

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add sharpdeveye/maestro --skill onboard-agent --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Onboard Agent?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Onboard Agent
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sharpdeveye-onboard-agent/badge)](https://www.skillsdirectory.com/skills/sharpdeveye-onboard-agent)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: onboard-agent
description: "Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch."
argument-hint: "[project or agent name]"
category: utility
version: 2.0.0
user-invocable: true
---

## 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

```markdown
## 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

```text
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

1. **System prompt**: Role definition with constraints
2. **2-3 essential tools**: Start with the minimum viable tool set
3. **Output schema**: Define expected output format
4. **One golden test**: At least one test case with known-good output
5. **Basic error handling**: Structured error responses
6. **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)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.