// Set 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>`.
| name | sylph-setup-skill |
| description | Set 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>`. |
| Connector | Purpose |
|---|---|
| Web Search | Find existing content, profiles, and examples |
| Web Fetch | Read blog posts, social profiles, published content |
| GitHub | Clone blog repos, read published articles |
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.
Run /sylph-setup-skill <name> after completing /sylph-setup (global setup). Run it once per channel or skill you want to activate.
/sylph-setup-skill linkedin
/sylph-setup-skill blog
/sylph-setup-skill newsletter
/sylph-setup-skill outbound
/sylph-setup-skill crm
...
_published/ and _examples/_insights.md with derived patternsEach guide is a markdown file in this folder:
| Skill | Guide | What it sets up |
|---|---|---|
setup-linkedin.md | Post voice, format rules, _insights, _examples | |
| Blog | setup-blog.md | Article structure, SEO patterns, _insights, _examples |
| Newsletter | setup-newsletter.md | Format, length, audience, _insights, _examples |
| Substack | setup-substack.md | Long-form voice, article structure, _insights |
| X / Twitter | setup-x.md | Tweet voice, thread format, _insights, _examples |
setup-reddit.md | Subreddit targets, tone, post types, _insights | |
| Website | setup-website.md | Copy voice, page templates, update workflow |
setup-email.md | Email voice, opener/closer patterns, templates | |
| Outbound | setup-outbound.md | Campaign structure, sequences, ICP targeting |
| CRM | setup-crm.md | CRM connection, pipeline stages, field mapping |
| Events | setup-events.md | Event types, templates, promotion workflow |
| Investor updates | setup-investor-update.md | Format, metrics, cadence |
| Brand | setup-brand.md | Visual identity, voice guide, asset templates |
| HR | setup-hr.md | Screening criteria, job templates, evaluation rubric |
| Slack community | setup-slack-community.md | Community tone, response patterns, channel rules |
| Customer report | setup-customer-report.md | 360 report template, data source mapping |
| Customer success | setup-customer-success.md | Follow-up cadence, CS backlog, templates |
| Zero inbox | setup-zero-inbox.md | Triage rules, routing logic, proxy senders |
| Create issue | setup-create-issue.md | GitHub issue conventions, labels, format |
| Contracts | setup-contracts.md | Legal details, contract templates, review rules |
When the user runs /sylph-setup-skill <name>:
Map the name to the corresponding setup guide file:
linkedin -> read setup-linkedin.mdblog -> read setup-blog.mdnewsletter -> read setup-newsletter.mdsubstack -> read setup-substack.mdx or twitter -> read setup-x.mdreddit -> read setup-reddit.mdwebsite -> read setup-website.mdemail -> read setup-email.mdoutbound -> read setup-outbound.mdcrm -> read setup-crm.mdevents -> read setup-events.mdinvestor-update or finance -> read setup-investor-update.mdbrand -> read setup-brand.mdhr or screening -> read setup-hr.mdslack-community or slack -> read setup-slack-community.mdcustomer-report -> read setup-customer-report.mdcustomer-success or cs -> read setup-customer-success.mdzero-inbox or inbox -> read setup-zero-inbox.mdcreate-issue or issues -> read setup-create-issue.mdcontracts or create-contract or review-contract -> read setup-contracts.mdFollow the guide step by step
After setup, generate a test piece to verify quality
If the name doesn't match any guide, list available options and ask the user to pick one.
Every skill setup follows the same 4-step pattern:
Before asking the user anything, search for and pull her existing content:
_published/For each piece found:
<channel>/_published/YYYY-MM-DD_slug.md with proper frontmatter<channel>/_examples/From the collected content, analyze and write to <channel>/_insights.md:
Show the insights to the user:
Here's what I learned from your existing [channel] content. What would you change?
Update the skill's SKILL.md with derived rules:
Generate one piece of content using the newly configured skill. Ask the user to review. Capture any edits as the first learning cycle in _insights.md.
Generate a customer-specific enterprise service agreement by filling in the standard template with deal details.
Head of Data agent - creates reportings and ad-hoc analytics using nao MCP tools. Always use ask_nao to create conversations that persist in nao.
Review a contract against standard negotiation positions - flag deviations, generate redlines, provide business impact analysis. Use when reviewing vendor or customer agreements, when you need clause-by-clause analysis, or when preparing a negotiation strategy.
Create a new skill from scratch. Generates the SKILL.md, registers it in AGENTS.md, and sets up the content folder structure.
Set up an AI agent by validating her scope, schedule, and delivery channel. Run as `/sylph-setup-agent <agent-name>` or `/sylph-setup-agent all`.
Personalize Sylph to your company. Ask the company name, then derive everything from the web - CONTEXT.md, brand voice, team, ICP, and standing instructions.