getnao/sylph / .claude/skills/sylph-setup-skill
sylph-setup-skill
VerifiedSet 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>`.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| setup-blog.md | markdown | 4.3 KB |
| setup-brand.md | markdown | 4.5 KB |
| setup-contracts.md | markdown | 5.8 KB |
| setup-create-issue.md | markdown | 4.9 KB |
| setup-crm.md | markdown | 2.5 KB |
| setup-customer-report.md | markdown | 5.9 KB |
| setup-customer-success.md | markdown | 5.8 KB |
| setup-email.md | markdown | 3.5 KB |
| setup-events.md | markdown | 3.8 KB |
| setup-hr.md | markdown | 4.2 KB |
| setup-investor-update.md | markdown | 3.1 KB |
| setup-linkedin.md | markdown | 5.1 KB |
| setup-newsletter.md | markdown | 4.9 KB |
| setup-outbound.md | markdown | 5.1 KB |
| setup-reddit.md | markdown | 4.1 KB |
| setup-slack-community.md | markdown | 6.0 KB |
| setup-substack.md | markdown | 4.0 KB |
| setup-website.md | markdown | 3.6 KB |
| setup-x.md | markdown | 3.6 KB |
| setup-zero-inbox.md | markdown | 6.6 KB |
setup-substack.md
View on GitHub# Setup: Substack
Guide for setting up the Substack long-form skill by auto-discovering voice, structure, and audience insights from the web.
## Prerequisites
- Global setup complete (`/sylph-setup`)
- Company name and CAO name available in `CONTEXT.md`
## Step 1: Find the Substack
1. Read `CONTEXT.md` for the company name, CAO name, and website URL.
2. Search for the Substack using multiple strategies:
- Use WebSearch: `"[CAO name]" site:substack.com`.
- Use WebSearch: `"[company name]" site:substack.com`.
- Check the company website for Substack links (footer, blog page, about page).
3. If found, read the Substack homepage and pull the 5-8 most recent articles.
4. If not found, ask the CAO: **"What's your Substack URL?"**
## Step 2: Auto-extract examples
From the articles found in Step 1:
1. Read the full content of each article.
2. Identify the 3-4 best-performing articles based on engagement signals (likes, comments, restacks).
3. For each top article, save to `content/substack/_examples/YYYY-MM-DD_slug.md`:
```yaml
---
date: YYYY-MM-DD
channel: substack
topic: [derived from content]
format: [essay | tutorial | opinion | interview | case-study]
status: published
performance:
likes: [number if visible]
comments: [number if visible]
restacks: [number if visible]
notes: "[why it likely performed - topic, structure, angle]"
---
```
## Step 3: Auto-derive insights
Analyze all pulled articles to derive patterns. Look for:
- **Length**: typical word count per article.
- **Structure**: how does she organize articles? (narrative arc, problem-solution, step-by-step, opinion piece)
- **Voice**: how does her Substack voice differ from other channels? More personal? More opinionated? More technical?
- **Opening patterns**: how do articles start? (personal anecdote, bold claim, question, data point)
- **Closing patterns**: how do articles end? (CTA, question, summary, call for comments)
- **Topics and themes**: what subjects does she cover? Any recurring series or columns?
- **Paywall usage**: is content free or paywalled? What's the pattern?
- **Cross-posting signals**: does she reference other platforms? Adapt content from elsewhere?
- **Cadence**: how often does she publish? (weekly, biweekly, monthly)
Write the analysis to `content/substack/_insights.md`:
```markdown
# Substack Insights
## Voice
- Tone: [how Substack voice differs from other channels]
- Personal level: [how much personal story vs pure analysis]
## What works
- Topics: [what drives views and engagement]
- Format: [essay, tutorial, opinion, etc.]
- Length: [optimal word count derived from articles]
- Hooks: [opening patterns that retain readers]
## What doesn't work
- [any patterns in lower-engagement articles]
## Structure
- Typical article flow: [intro -> ... -> conclusion]
- Recurring sections: [any series or columns identified]
## Paywall strategy
- Free: [what's free]
- Paid: [what's paywalled, if applicable]
## Cross-posting
- [any cross-posting patterns observed]
## Cadence
- [publishing frequency derived from dates]
## Performance benchmarks
- Good post: [X] likes, [Y] comments (derived from data)
- Top post: [X] likes, [Y] comments (derived from best performers)
```
## Step 4: Confirm with the CAO
Present the derived insights summary to the CAO:
> "I analyzed your Substack and found: you publish [cadence], averaging [length] words. Your articles tend to follow a [structure] pattern, with a [voice description] voice. Your strongest pieces are about [topics]. Does this match? Anything to correct?"
Incorporate her corrections. Ask for any private data she'd like to add (subscriber count, open rates, growth drivers).
## Step 5: Configure the skill
Open `.claude/skills/content/substack-writer/SKILL.md` and fill in:
- Long-form structure template (from analysis)
- Voice calibration (personal level, opinion level)
- Cross-posting rules
- Paywall decision criteria
- Audience description
## Step 6: Test generation
Generate one Substack article outline + opening section on a topic the CAO picks. Ask for feedback. Capture edits in `content/substack/_insights.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |