$npx -y skills add getnao/sylph --skill sylph-setup-skillSet up a specific Sylph skill by auto-pulling examples from the web, deriving insights, and configuring the skill. Run as /sylph-setup-skill <skill-name>.
| 1 | # Setup Skill |
| 2 | |
| 3 | ## MCP connectors |
| 4 | |
| 5 | | Connector | Purpose | |
| 6 | |-----------|---------| |
| 7 | | Web Search | Find existing content, profiles, and examples | |
| 8 | | Web Fetch | Read blog posts, social profiles, published content | |
| 9 | | GitHub | Clone blog repos, read published articles | |
| 10 | |
| 11 | ## Core principle: ask less, derive more |
| 12 | |
| 13 | **Ask the user as few things as possible.** For most channels, the agent can find existing content online (website, LinkedIn, blog, Twitter, Substack). Pull it, analyze it, derive insights and voice - then show the user for confirmation. Only ask when you genuinely can't find something. |
| 14 | |
| 15 | ## When to use |
| 16 | |
| 17 | Run `/sylph-setup-skill <name>` after completing `/sylph-setup` (global setup). Run it once per channel or skill you want to activate. |
| 18 | |
| 19 | ## Usage |
| 20 | |
| 21 | ``` |
| 22 | /sylph-setup-skill linkedin |
| 23 | /sylph-setup-skill blog |
| 24 | /sylph-setup-skill newsletter |
| 25 | /sylph-setup-skill outbound |
| 26 | /sylph-setup-skill crm |
| 27 | ... |
| 28 | ``` |
| 29 | |
| 30 | ## How it works |
| 31 | |
| 32 | 1. Read the setup guide for the requested skill (from this folder) |
| 33 | 2. Auto-discover and pull existing content from the web or connected repos |
| 34 | 3. Copy the best examples to `_published/` and `_examples/` |
| 35 | 4. Derive insights (voice, tone, format, what works) from the examples |
| 36 | 5. Update the skill's SKILL.md with derived rules |
| 37 | 6. Update the channel's `_insights.md` with derived patterns |
| 38 | 7. Show the user for confirmation and corrections |
| 39 | |
| 40 | --- |
| 41 | |
| 42 | ## Available setup guides |
| 43 | |
| 44 | Each guide is a markdown file in this folder: |
| 45 | |
| 46 | | Skill | Guide | What it sets up | |
| 47 | |-------|-------|-----------------| |
| 48 | | LinkedIn | `setup-linkedin.md` | Post voice, format rules, _insights, _examples | |
| 49 | | Blog | `setup-blog.md` | Article structure, SEO patterns, _insights, _examples | |
| 50 | | Newsletter | `setup-newsletter.md` | Format, length, audience, _insights, _examples | |
| 51 | | Substack | `setup-substack.md` | Long-form voice, article structure, _insights | |
| 52 | | X / Twitter | `setup-x.md` | Tweet voice, thread format, _insights, _examples | |
| 53 | | Reddit | `setup-reddit.md` | Subreddit targets, tone, post types, _insights | |
| 54 | | Website | `setup-website.md` | Copy voice, page templates, update workflow | |
| 55 | | Email | `setup-email.md` | Email voice, opener/closer patterns, templates | |
| 56 | | Outbound | `setup-outbound.md` | Campaign structure, sequences, ICP targeting | |
| 57 | | CRM | `setup-crm.md` | CRM connection, pipeline stages, field mapping | |
| 58 | | Events | `setup-events.md` | Event types, templates, promotion workflow | |
| 59 | | Investor updates | `setup-investor-update.md` | Format, metrics, cadence | |
| 60 | | Brand | `setup-brand.md` | Visual identity, voice guide, asset templates | |
| 61 | | HR | `setup-hr.md` | Screening criteria, job templates, evaluation rubric | |
| 62 | | Slack community | `setup-slack-community.md` | Community tone, response patterns, channel rules | |
| 63 | | Customer report | `setup-customer-report.md` | 360 report template, data source mapping | |
| 64 | | Customer success | `setup-customer-success.md` | Follow-up cadence, CS backlog, templates | |
| 65 | | Zero inbox | `setup-zero-inbox.md` | Triage rules, routing logic, proxy senders | |
| 66 | | Create issue | `setup-create-issue.md` | GitHub issue conventions, labels, format | |
| 67 | | Contracts | `setup-contracts.md` | Legal details, contract templates, review rules | |
| 68 | |
| 69 | --- |
| 70 | |
| 71 | ## Dispatch logic |
| 72 | |
| 73 | When the user runs `/sylph-setup-skill <name>`: |
| 74 | |
| 75 | 1. Map the name to the corresponding setup guide file: |
| 76 | - `linkedin` -> read `setup-linkedin.md` |
| 77 | - `blog` -> read `setup-blog.md` |
| 78 | - `newsletter` -> read `setup-newsletter.md` |
| 79 | - `substack` -> read `setup-substack.md` |
| 80 | - `x` or `twitter` -> read `setup-x.md` |
| 81 | - `reddit` -> read `setup-reddit.md` |
| 82 | - `website` -> read `setup-website.md` |
| 83 | - `email` -> read `setup-email.md` |
| 84 | - `outbound` -> read `setup-outbound.md` |
| 85 | - `crm` -> read `setup-crm.md` |
| 86 | - `events` -> read `setup-events.md` |
| 87 | - `investor-update` or `finance` -> read `setup-investor-update.md` |
| 88 | - `brand` -> read `setup-brand.md` |
| 89 | - `hr` or `screening` -> read `setup-hr.md` |
| 90 | - `slack-community` or `slack` -> read `setup-slack-community.md` |
| 91 | - `customer-report` -> read `setup-customer-report.md` |
| 92 | - `customer-success` or `cs` -> read `setup-customer-success.md` |
| 93 | - `zero-inbox` or `inbox` -> read `setup-zero-inbox.md` |
| 94 | - `create-issue` or `issues` -> read `setup-create-issue.md` |
| 95 | - `contracts` or `create-contract` or `review-contract` -> read `setup-contracts.md` |
| 96 | |
| 97 | 2. Follow the guide step by step |
| 98 | 3. After setup, generate a test piece to verify quality |
| 99 | |
| 100 | If the name doesn't match any guide, list available options and ask the user to pick one. |
| 101 | |
| 102 | --- |
| 103 | |
| 104 | ## Universal setup pattern |
| 105 | |
| 106 | Every skill setup follows the same 4-step pattern: |
| 107 | |
| 108 | ### Step 1: Auto-discover existing content |
| 109 | |
| 110 | Before asking the user anything, search for and pull her existing content: |
| 111 | |
| 112 | - **LinkedIn**: search her company LinkedIn page, read recent posts |
| 113 | - **Blog**: ask for the |