sylph-setup-agent
starsforks
How to install sylph-setup-agent?
getnao/sylph/sylph-setup-agent
$npx -y skills add getnao/sylph --skill sylph-setup-agentSet up an AI agent by validating her scope, schedule, and delivery channel. Run as /sylph-setup-agent <agent-name> or /sylph-setup-agent all.
SKILL.md
| 1 | # Setup Agent |
| 2 | |
| 3 | ## MCP connectors |
| 4 | |
| 5 | | Connector | Purpose | |
| 6 | |-----------|---------| |
| 7 | | Slack | Validate the Chief of Staff delivery channel | |
| 8 | |
| 9 | ## Core principle: derive from ROLE.md, confirm with the CAO |
| 10 | |
| 11 | Each agent already has a `ROLE.md` and `PROMPT.md` in `agents/<name>/`. Read them first. Derive scope, tasks, and cadence from those files. Only ask the CAO to confirm. |
| 12 | |
| 13 | ## When to use |
| 14 | |
| 15 | Run `/sylph-setup-agent <name>` after completing `/sylph-setup` (global setup) and before scheduling any agent. Run it once per agent you want to activate. |
| 16 | |
| 17 | ## Usage |
| 18 | |
| 19 | ``` |
| 20 | /sylph-setup-agent chief-of-staff |
| 21 | /sylph-setup-agent cmo |
| 22 | /sylph-setup-agent all |
| 23 | ``` |
| 24 | |
| 25 | ## Available agents |
| 26 | |
| 27 | | Agent | Directory | Default cadence | |
| 28 | |-------|-----------|----------------| |
| 29 | | chief-of-staff | `agents/chief-of-staff/` | Daily 08:00 | |
| 30 | | cmo | `agents/cmo/` | Daily (content), Weekly (planning) | |
| 31 | | product-manager | `agents/product-manager/` | Daily | |
| 32 | | customer-success | `agents/customer-success/` | Weekly (Monday) | |
| 33 | | head-of-data | `agents/head-of-data/` | Daily | |
| 34 | | head-of-sales | `agents/head-of-sales/` | Daily | |
| 35 | | executive-assistant | `agents/executive-assistant/` | Daily | |
| 36 | | brand-designer | `agents/brand-designer/` | On-demand | |
| 37 | |
| 38 | --- |
| 39 | |
| 40 | ## How it works |
| 41 | |
| 42 | ### Step 1: Read the agent definition |
| 43 | |
| 44 | 1. Read `agents/<name>/ROLE.md` for identity, responsibilities, decision boundaries, and tone |
| 45 | 2. Read `agents/<name>/PROMPT.md` for the execution routine |
| 46 | 3. Read `CONTEXT.md` for company context |
| 47 | |
| 48 | From these files, derive: |
| 49 | - **Scope**: what this agent owns (list of responsibilities from ROLE.md) |
| 50 | - **Tasks**: the concrete steps she runs (from PROMPT.md routine) |
| 51 | - **Default cadence**: how often she runs (from ROLE.md "Working rhythm" or similar) |
| 52 | - **Outputs**: what she produces and where it goes (from ROLE.md "Output rules") |
| 53 | - **Dependencies**: which other agents or tools she needs |
| 54 | |
| 55 | ### Step 2: Confirm scope and schedule |
| 56 | |
| 57 | Present the derived scope to the CAO: |
| 58 | |
| 59 | > Here's what **[agent name]** will do: |
| 60 | > |
| 61 | > **Scope:** |
| 62 | > - [responsibility 1 from ROLE.md] |
| 63 | > - [responsibility 2] |
| 64 | > - [responsibility 3] |
| 65 | > |
| 66 | > **She produces:** |
| 67 | > - [output 1 and where it goes] |
| 68 | > - [output 2] |
| 69 | > |
| 70 | > **She escalates to you:** |
| 71 | > - [escalation 1 from decision boundaries] |
| 72 | > - [escalation 2] |
| 73 | > |
| 74 | > **Proposed schedule:** [cadence from ROLE.md, e.g. "Daily at 08:00"] |
| 75 | > |
| 76 | > Anything to add, remove, or change? |
| 77 | |
| 78 | Incorporate the CAO's corrections. If the CAO adjusts the schedule, note it. |
| 79 | |
| 80 | ### Step 3: Chief of Staff only - validate Slack delivery |
| 81 | |
| 82 | The Chief of Staff is the only agent that writes to Slack. She delivers her daily briefing as a Slack DM to the CAO. |
| 83 | |
| 84 | **Only for chief-of-staff:** |
| 85 | |
| 86 | 1. **Connect to Slack** - if not already connected, ask the CAO to connect the Slack MCP |
| 87 | 2. **Ask the CAO:** |
| 88 | |
| 89 | > Where should the Chief of Staff deliver her daily briefing? (Slack DM to you, or a specific channel?) |
| 90 | |
| 91 | 3. **Validate the channel or DM exists** via Slack MCP |
| 92 | 4. **Save the Slack user ID or channel ID** for delivery |
| 93 | |
| 94 | For all other agents, skip this step. Other agents write to the repo (`_drafts/`, `_logs/`, `_plans/`) and deliver in chat. They don't post to Slack. |
| 95 | |
| 96 | ### Step 4: Write agent config |
| 97 | |
| 98 | Create or update `agents/<name>/CONFIG.md` with the confirmed settings: |
| 99 | |
| 100 | ```markdown |
| 101 | --- |
| 102 | agent: [name] |
| 103 | status: active |
| 104 | --- |
| 105 | |
| 106 | # [Agent Name] - Configuration |
| 107 | |
| 108 | ## Schedule |
| 109 | - Cadence: [daily / weekly / on-demand] |
| 110 | - Time: [HH:MM local time, if scheduled] |
| 111 | - Special: [e.g. "Monday: extended run with weekly planning"] |
| 112 | |
| 113 | ## Scope |
| 114 | - [responsibility 1] |
| 115 | - [responsibility 2] |
| 116 | - [responsibility 3] |
| 117 | |
| 118 | ## Escalation rules |
| 119 | - [what she escalates to the CAO] |
| 120 | |
| 121 | ## Dependencies |
| 122 | - Agents: [other agents she delegates to or receives from] |
| 123 | - Tools: [MCP connectors she needs] |
| 124 | ``` |
| 125 | |
| 126 | For the Chief of Staff only, add the delivery section: |
| 127 | |
| 128 | ```markdown |
| 129 | ## Delivery |
| 130 | - Channel: [Slack DM or channel name] |
| 131 | - Channel ID: [Slack channel/user ID] |
| 132 | - Fallback: chat message (if Slack fails) |
| 133 | ``` |
| 134 | |
| 135 | ### Step 5: Schedule the Chief of Staff as a cloud agent |
| 136 | |
| 137 | The Chief of Staff should run automatically every morning. After writing her CONFIG.md: |
| 138 | |
| 139 | 1. **Create a scheduled remote agent** using the scheduling system (Claude Code's `/schedule` or equivalent) |
| 140 | 2. **Configure the schedule:** |
| 141 | - **Trigger**: cron, daily at the CAO's preferred time (default: 08:00 local) |
| 142 | - **Prompt**: "Run the chief-of-staff routine: load ROLE.md and PROMPT.md from agents/chief-of-staff/, execute the full daily routine, commit the briefing, and deliver via Slack DM." |
| 143 | - **Monday variant**: the routine automatically branches for weekly planning (this is handled in PROMPT.md, no separate schedule needed) |
| 144 | 3. **Verify the schedule is active** and show the CAO a confirmation: |
| 145 | |
| 146 | > Chief of Staff is now scheduled to run every day at [HH:MM]. She'll deliver her briefing to [Slack channel/DM]. You can also invoke |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
