website
starsforks
How to install website?
getnao/sylph/website
$npx -y skills add getnao/sylph --skill website---
SKILL.md
| 1 | # Website Content Updater |
| 2 | |
| 3 | ```yaml |
| 4 | name: website-updater |
| 5 | description: > |
| 6 | Reviews and updates website pages. Creates PRs for content changes, |
| 7 | handles page-specific patterns, and ensures consistency. |
| 8 | triggers: |
| 9 | - update the website |
| 10 | - website copy |
| 11 | - landing page |
| 12 | - fix the homepage |
| 13 | ``` |
| 14 | |
| 15 | --- |
| 16 | |
| 17 | ## MCP connectors |
| 18 | |
| 19 | | Connector | Purpose | |
| 20 | |-----------|---------| |
| 21 | | GitHub | Push changes, create PRs for site updates | |
| 22 | |
| 23 | ## Review Workflow |
| 24 | |
| 25 | ### Step 1: Audit Current State |
| 26 | Before making changes, review: |
| 27 | - Fetch the live page via `WebFetch` to see current copy |
| 28 | - Read the source files in the repo |
| 29 | - Note what needs updating and why |
| 30 | |
| 31 | ### Step 2: Make Changes |
| 32 | - Edit source files directly |
| 33 | - Follow page-specific patterns (below) |
| 34 | - Maintain consistent voice and formatting across pages |
| 35 | |
| 36 | ### Step 3: Create PR |
| 37 | ```bash |
| 38 | git checkout -b content/website/YYYY-MM-DD-description |
| 39 | # make changes |
| 40 | git add [changed files] |
| 41 | git commit -m "content: update [page] - [what changed]" |
| 42 | # create PR for review |
| 43 | ``` |
| 44 | |
| 45 | ### Step 4: Preview |
| 46 | - Run the local dev server if available |
| 47 | - Verify changes render correctly |
| 48 | - Check mobile responsiveness |
| 49 | - Verify all links work |
| 50 | |
| 51 | --- |
| 52 | |
| 53 | ## Page-Specific Patterns |
| 54 | |
| 55 | ### Homepage |
| 56 | - Hero: one sentence value proposition + one sentence supporting detail |
| 57 | - Social proof: specific numbers or customer logos, not vague claims |
| 58 | - CTA: one primary action, one secondary |
| 59 | - Keep above-the-fold tight - no scrolling to understand what you do |
| 60 | |
| 61 | ### Product/Features Page |
| 62 | - Lead with the problem each feature solves |
| 63 | - Use before/after or with/without framing |
| 64 | - Screenshots or GIFs for every feature |
| 65 | - Keep descriptions to 2-3 sentences per feature |
| 66 | |
| 67 | ### Pricing Page |
| 68 | - Make the recommended plan obvious |
| 69 | - List what's included, not what's excluded |
| 70 | - Address "What happens when I hit the limit?" upfront |
| 71 | - Include FAQ section for common pricing questions |
| 72 | |
| 73 | ### About Page |
| 74 | - Team section: real photos, real titles, one sentence per person |
| 75 | - Mission: what you do and why, in 2 sentences |
| 76 | - Values: only if they're specific enough to be actionable |
| 77 | |
| 78 | ### Blog Index |
| 79 | - Show title, date, author, and reading time |
| 80 | - Category filters should work |
| 81 | - Featured post gets prominent placement |
| 82 | |
| 83 | --- |
| 84 | |
| 85 | ## Content Rules |
| 86 | |
| 87 | - No em dashes. Use hyphens (-) or colons (:). |
| 88 | - No "cutting-edge", "revolutionary", or "world-class" |
| 89 | - Specific numbers beat vague claims ("500+ teams" beats "many teams") |
| 90 | - Every page should have exactly one primary CTA |
| 91 | - Alt text on every image |
| 92 | - Meta descriptions on every page (under 160 characters) |
| 93 | - Check that Open Graph tags are set for social sharing |
| 94 | |
| 95 | ## Self-improvement |
| 96 | |
| 97 | After the CAO reviews and approves website copy: |
| 98 | |
| 99 | 1. Move the final version from `_drafts/` to `_published/` |
| 100 | 2. Diff what was drafted vs what the CAO kept - identify patterns in her edits to headlines, CTAs, or page structure |
| 101 | 3. Update `content/website/_insights.md` with what worked and what she changed |
| 102 | 4. If her edits reveal a new rule (e.g. "hero must mention the ICP by name", "never use more than one CTA per section"), add it to the Content Rules or Page-Specific Patterns sections above |
| 103 | 5. If a page performs well (high conversion, low bounce), save it to `content/website/_examples/` with performance annotations |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
