sylph-setup
starsforks
How to install sylph-setup?
getnao/sylph/sylph-setup
$npx -y skills add getnao/sylph --skill sylph-setupPersonalize Sylph to your company. Ask the company name, then derive everything from the web - CONTEXT.md, brand voice, team, ICP, and standing instructions.
SKILL.md
| 1 | # Setup Sylph |
| 2 | |
| 3 | ## MCP connectors |
| 4 | |
| 5 | | Connector | Purpose | |
| 6 | |-----------|---------| |
| 7 | | Web Search | Search for company info, team, socials | |
| 8 | | Web Fetch | Read company website, about page, blog, LinkedIn | |
| 9 | |
| 10 | ## Core principle: ask less, derive more |
| 11 | |
| 12 | **Ask the user as few things as possible.** The only required input is the company name. Everything else should be derived from the web - website, LinkedIn, social profiles, blog, job postings, press coverage. Only ask the user to confirm and correct what you found. |
| 13 | |
| 14 | ## When to use |
| 15 | |
| 16 | Run `/sylph-setup` right after forking the repo, before using any other skill. |
| 17 | |
| 18 | ## What it does |
| 19 | |
| 20 | 1. Asks the company name (and optionally website URL) |
| 21 | 2. Searches the web and reads the company's website, socials, and public info |
| 22 | 3. Auto-fills `CONTEXT.md` with derived company details |
| 23 | 4. Seeds `.claude/MEMORY.md` with initial preferences |
| 24 | 5. Generates brand voice guidelines in `brand/guidelines/` |
| 25 | 6. Configures the agent roster in `agents/` |
| 26 | |
| 27 | --- |
| 28 | |
| 29 | ## Step 0: Meet the CAO |
| 30 | |
| 31 | Before anything else, welcome the user as the **Chief Agent Officer (CAO)** - the human who will review, approve, and have final say over everything the agents produce. |
| 32 | |
| 33 | Ask: |
| 34 | |
| 35 | > **Welcome, Chief Agent Officer.** You're about to set up your company's AI brain. Before we start: |
| 36 | > |
| 37 | > 1. **What's your name?** |
| 38 | > 2. **What are your pronouns?** (she/her, he/him, they/them, etc.) |
| 39 | |
| 40 | Store their name and pronouns in `.claude/MEMORY.md` so all agents and skills use them consistently. |
| 41 | |
| 42 | Update `AGENTS.md` definition: replace the generic CAO description with their name and pronouns. |
| 43 | |
| 44 | If the user's pronouns are **she/her**, add this message: |
| 45 | |
| 46 | > By the way - Sylph's creator Claire wanted me to tell you: she's happy to see a fellow tech sister on this repo. Welcome, Queen. 💜👸 |
| 47 | |
| 48 | --- |
| 49 | |
| 50 | ## Step 1: Company discovery (automated) |
| 51 | |
| 52 | Ask the user ONE question: |
| 53 | |
| 54 | > **What's your company name?** (and website URL if it's not obvious) |
| 55 | |
| 56 | Then derive everything automatically: |
| 57 | |
| 58 | ### Web research |
| 59 | |
| 60 | 1. **Search the web** for the company name - find the website, LinkedIn company page, Twitter/X, GitHub, Crunchbase, press articles |
| 61 | 2. **Read the website** - homepage, about page, pricing page, docs, careers page |
| 62 | 3. **Read the LinkedIn company page** - description, team size, industry, recent posts |
| 63 | 4. **Read Crunchbase/press** - funding stage, investors, founding date, location |
| 64 | 5. **Read GitHub** (if applicable) - repos, tech stack, open source status |
| 65 | |
| 66 | ### Fill CONTEXT.md from research |
| 67 | |
| 68 | From the web research, fill in every section of `CONTEXT.md`: |
| 69 | |
| 70 | | Section | Source | |
| 71 | |---------|--------| |
| 72 | | What the company does | Website homepage + about page | |
| 73 | | The problem it solves | Website homepage + pricing page copy | |
| 74 | | How the product works | Docs, product page, or demo page | |
| 75 | | ICP | Pricing page, case studies, job descriptions | |
| 76 | | Team | About page, LinkedIn, careers page | |
| 77 | | Integrations | Docs, integrations page, product page | |
| 78 | | Company basics | Crunchbase, LinkedIn, footer of website | |
| 79 | | Key terminology | Docs, blog, product page | |
| 80 | | Standing instructions | Derive from brand voice observed on website + socials | |
| 81 | |
| 82 | ### Present findings to the user |
| 83 | |
| 84 | Show the user the draft CONTEXT.md and ask: |
| 85 | |
| 86 | > Here's what I found about [company]. Review this and tell me what to fix. I'll update it. |
| 87 | |
| 88 | Only ask follow-up questions for things you genuinely couldn't find online (internal terminology, specific process rules, preferred tools). |
| 89 | |
| 90 | Use the CAO's name in conversations (not "user" or "you"). Use their stated pronouns in all generated files. |
| 91 | |
| 92 | ### After filling in CONTEXT.md |
| 93 | |
| 94 | - Verify the file reads naturally top to bottom |
| 95 | - Ensure no `[placeholder]` markers remain |
| 96 | - Commit: "Initialize company context" |
| 97 | |
| 98 | --- |
| 99 | |
| 100 | ## Step 2: Memory bootstrap |
| 101 | |
| 102 | Ask the user ONE question: |
| 103 | |
| 104 | > **Any rules or preferences I should know about?** (tool quirks, process rules, voice preferences, things to always/never do) |
| 105 | |
| 106 | Write each answer as a dated entry in `.claude/MEMORY.md`. If she has nothing yet, that's fine - memory will grow as she uses skills. |
| 107 | |
| 108 | --- |
| 109 | |
| 110 | ## Step 3: Brand voice (derived from web) |
| 111 | |
| 112 | **Do not ask the user to describe her brand voice.** Instead: |
| 113 | |
| 114 | 1. Read 3-5 pieces of content from her website (blog posts, landing pages, about page) |
| 115 | 2. Read her recent LinkedIn or Twitter posts |
| 116 | 3. Analyze the writing patterns: sentence length, vocabulary level, tone, favorite constructions, words she uses vs avoids |
| 117 | |
| 118 | Generate `brand/guidelines/voice.md` from the analysis: |
| 119 | |
| 120 | - 3 adjectives that describe the voice |
| 121 | - Sentence structure patterns (short/long, fragments OK, etc.) |
| 122 | - Words and phrases she uses frequently |
| 123 | - Words and phrases she never uses |
| 124 | - Tone differences by channel (if visible from web vs social) |
| 125 | |
| 126 | Show the draft to the user: |
| 127 | |
| 128 | > Here's the voice guide I derived from your existing content. What would you change? |
| 129 | |
| 130 | Upd |
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
