grow

GitHub

追踪已发布产品的增长指标,包括性能、开发速度、SEO及依赖健康度。通过数据收集与深度分析,提供战略洞察和优先改进建议,帮助独立开发者优化产品表现。

skills/grow/SKILL.md Houseofmvps/ultraship

Trigger Scenarios

检查项目增长指标 查看SEO趋势 评估部署频率 获取整体项目健康状况报告

Install

npx skills add Houseofmvps/ultraship --skill grow -g -y
More Options

Use without installing

npx skills use Houseofmvps/ultraship@grow

指定 Agent (Claude Code)

npx skills add Houseofmvps/ultraship --skill grow -a claude-code -g -y

安装 repo 全部 skill

npx skills add Houseofmvps/ultraship --all -g -y

预览 repo 内 skill

npx skills add Houseofmvps/ultraship --list

SKILL.md

Frontmatter
{
    "name": "grow",
    "description": "Post-Ship Growth Intelligence — track how your shipped product is performing. Use when user wants to check growth metrics, SEO trajectory, uptime, deploy frequency, or overall project health over time.",
    "allowed-tools": "Bash, Read, Grep, Glob",
    "argument-hint": "<production-url>"
}

Post-Ship Growth Intelligence

Most indie builders ship and forget. The ones who win ship and measure. This skill makes growth visible, trackable, and actionable — like having a growth-stage CTO and a marketing analyst looking at your dashboards every week.

Process

Phase 1: Collect Metrics

node ${CLAUDE_PLUGIN_ROOT}/tools/growth-tracker.mjs <project-directory> --url=<production-url> --save

Parse the JSON output for current snapshot and historical trends.

Phase 2: Growth Dashboard

Present a clear growth report:

Uptime & Performance:

  • Current status (up/down/degraded)
  • Response time trend (faster? slower?)
  • Compare to previous snapshot
  • Context: response time under 500ms is good, under 200ms is excellent, over 1s is a problem

Development Velocity:

  • Commits this week vs last week
  • Deploy frequency (30-day trend)
  • Active development days
  • Lines added vs removed (net growth)
  • Context: healthy velocity for a solo founder is 3-5 deploys/week. Less than 1 deploy/week means either the project is stable or stalling — check which.

SEO + AI visibility Trajectory:

  • Current SEO + AI visibility scores
  • Change since last check
  • Trend direction (improving/declining/stable)
  • Context: SEO score above 80 is solid, GEO above 70 means AI search engines can find and cite you, below 50 means you're invisible to AI search

Dependency Health:

  • Outdated packages count
  • Security vulnerabilities
  • Action needed?

Code Health:

  • Quality score trend
  • Improving or declining?

Phase 3: Growth Insights

Based on the data, provide strategic insights — not just metrics, but what they mean:

1. What's going well — metrics that are improving 2. What needs attention — metrics that are declining or stagnant 3. Benchmarks — how these metrics compare to typical indie SaaS projects:

Metric Below Average Average Good Excellent
Response time >1s 500ms-1s 200-500ms <200ms
Deploy frequency <1/week 1-2/week 3-5/week Daily
SEO score <50 50-70 70-85 85+
GEO score <40 40-60 60-80 80+
Vulnerabilities >5 high 1-5 high 0 high 0 total

4. The "One Thing" recommendation — if you could only do one thing this week to improve growth, what is it? Prioritize ruthlessly. Solo founders don't have time for 15 action items.

Phase 4: SEO Deep Dive (if GSC credentials available)

node ${CLAUDE_PLUGIN_ROOT}/tools/gsc-client.mjs query <site-url> 28

Show:

  • Top keywords you rank for
  • Ranking changes (up/down movers)
  • New keywords discovered
  • Click-through rates
  • Strategic analysis: Which keywords are worth doubling down on? Which are vanity metrics?

Content gap identification:

  • Keywords you rank 5-20 for (striking distance — could reach page 1 with targeted content)
  • Keywords competitors rank for that you don't (use with /compete data)
  • Long-tail keywords with low competition but high intent

Phase 5: Bing Indexing Status (if Bing key available)

node ${CLAUDE_PLUGIN_ROOT}/tools/bing-webmaster.mjs url-info <site-url> <page-url>

Show indexing status across Bing (which also powers ChatGPT Search and DuckDuckGo).

Why this matters for AI search: If Bing hasn't indexed your pages, ChatGPT Search can't find you. Submit your sitemap to Bing and verify key pages are indexed.

Phase 6: Growth Strategy by Stage

Tailor recommendations to where the product is:

Pre-launch (0 users):

  • Focus: landing page SEO, GEO readiness, community building
  • Key metric: email signups, waitlist size
  • Action: build in public, share progress, collect early feedback

Post-launch (1-100 users):

  • Focus: activation rate, first-week retention, user feedback loops
  • Key metric: signup → activation conversion rate
  • Action: talk to every user, fix the top 3 onboarding friction points

Growth (100-1000 users):

  • Focus: organic acquisition, content marketing, SEO compounding
  • Key metric: organic traffic growth rate, MRR
  • Action: publish 2-4 SEO-optimized articles/month, build referral loops

Scale (1000+ users):

  • Focus: retention, expansion revenue, operational efficiency
  • Key metric: net revenue retention, churn rate, LTV/CAC
  • Action: automate onboarding, build self-serve, reduce support load

Phase 7: Action Items

Generate a prioritized list:

  1. Quick wins — things you can do today (15 min or less)
  2. This week — improvements that take a few hours
  3. This month — strategic investments for long-term growth

Phase 8: Weekly Digest Format

If the user wants a recurring check, format as a weekly digest:

Weekly Growth Report — [Project Name]
Week of [date]

Uptime: 99.9% | Avg Response: 230ms (-15ms)
SEO: 85 (+3) | GEO: 72 (+2) | AEO: 68 (+5)
Commits: 15 | Deploys: 3 | Active Days: 5
Vulnerabilities: 0 critical, 1 high

Top Action: Update 3 outdated dependencies

Trend: Improving (3 consecutive weeks of SEO gains)

Key Principles

  • What gets measured gets improved. Run this weekly. Growth is invisible without data.
  • One thing at a time. Solo founders can't do 15 things. Recommend the highest-impact single action.
  • Compounding beats spikes. A 2% weekly improvement in SEO score compounds to 180% over a year. Consistency wins.
  • GEO is the new SEO. In 2026, AI search visibility is as important as Google ranking. Track both.

Version History

  • ed232cb Current 2026-07-24 16:15

Same Skill Collection

skills/a11y/SKILL.md
skills/architecture/SKILL.md
skills/brainstorming/SKILL.md
skills/canary/SKILL.md
skills/clone-patterns/SKILL.md
skills/code-review/SKILL.md
skills/compete/SKILL.md
skills/cost/SKILL.md
skills/demo/SKILL.md
skills/deploy/SKILL.md
skills/dispatching-parallel-agents/SKILL.md
skills/evals/SKILL.md
skills/executing-plans/SKILL.md
skills/finishing-a-development-branch/SKILL.md
skills/frontend-design/SKILL.md
skills/guard/SKILL.md
skills/index-fix/SKILL.md
skills/investigate/SKILL.md
skills/launch/SKILL.md
skills/learn/SKILL.md
skills/onboard/SKILL.md
skills/pentest/SKILL.md
skills/perf-audit/SKILL.md
skills/receiving-code-review/SKILL.md
skills/release/SKILL.md
skills/requesting-code-review/SKILL.md
skills/rescue/SKILL.md
skills/retro/SKILL.md
skills/revise-claude-md/SKILL.md
skills/security-audit/SKILL.md
skills/seo-audit/SKILL.md
skills/seo-strategy/SKILL.md
skills/ship-gate/SKILL.md
skills/sprint/SKILL.md
skills/staying-current/SKILL.md
skills/subagent-driven-development/SKILL.md
skills/systematic-debugging/SKILL.md
skills/test-driven-development/SKILL.md
skills/using-git-worktrees/SKILL.md
skills/using-ultraship/SKILL.md
skills/verification-before-completion/SKILL.md
skills/visual-diff/SKILL.md
skills/writing-plans/SKILL.md
skills/writing-skills/SKILL.md

Metadata

Files
0
Version
ed232cb
Hash
08b30720
Indexed
2026-07-24 16:15

inicio - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-16 21:27
浙ICP备14020137号-1 $mapa de visitantes$