All categories
Business & Operations
Operations, strategy, finance, sales, support, management, and planning
- 35,322
- 1,472
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse business & operations skills
Showing 13,969–13,992 of 35,322 skills
- Review BacklogReview and promote backlog items to active milestoneVotes: 0GitHub stars: 90
- NextAutomatically advance to the next logical step in the GSD workflowVotes: 0GitHub stars: 90
- Milestone SummaryGenerate a comprehensive project summary from milestone artifacts for team onboarding and reviewVotes: 0GitHub stars: 90
- List Phase AssumptionsSurface Claude's assumptions about a phase approach before planningVotes: 0GitHub stars: 90
- Ingest DocsScan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.Votes: 0GitHub stars: 90
- HealthDiagnose planning directory health and optionally repair issuesVotes: 0GitHub stars: 90
- From Gsd2Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) formatVotes: 0GitHub stars: 90
- Ai Integration PhaseGenerate AI design contract (AI-SPEC.md) for phases that involve building AI systems — framework selection, implementation guidance from official docs, and evaluation strategyVotes: 0GitHub stars: 90
- Add BacklogAdd an idea to the backlog parking lot (999.x numbering)Votes: 0GitHub stars: 90
- To TicketsBreak a plan, spec, or the current conversation into vertical tracer-bullet tickets, each declaring the tickets that block it — written as one file per ticket under plans/<plan-dir>/tickets/, or published as issue-tracker sub-tasks under a parent issue on explicit opt-in. Use when a plan needs slicing into independently shippable units, when work is handed to parallel agents or devs, or when a wide refactor needs an expand–contract sequence. Triggers on "break this into tickets", "slice the p...Votes: 0GitHub stars: 3
- RetroFacilitate team retrospectives — structured backward-looking reflection on completed sprints, features, or incidents to extract lessons and drive continuous improvement.Votes: 0GitHub stars: 3
- AskAnswer technical and architectural questions about the codebase with researched, in-depth, context-aware responses (not superficial replies). Reads relevant code files, references specific files + line numbers, and explains architectural decisions / patterns found in actual code. Use when user asks "how is X implemented?", "what's the schema for Y?", "explain Z in this project", or any technical / architectural consultation request.Votes: 0GitHub stars: 3
- Seo TechnicalTechnical SEO audit across 9 categories — crawlability, indexability, security, URL structure, mobile/page experience, Core Web Vitals, structured-data detection, JavaScript rendering, and IndexNow. Also covers agent-friendly-page auditing (accessibility tree, agentic browsing). Use for "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", "security headers", or an existing-site inventory before a writing campaign.Votes: 0GitHub stars: 3
- Seo SitemapXML sitemap analysis and generation — validate an existing sitemap against Google's real rules (50k/50MB caps, lastmod accuracy, extension subtypes), or generate a new one (with index splitting) for a site being built out. Feeds the technical-SEO audit and the sitemap step of the seo-writing pipeline's publish stage.Votes: 0GitHub stars: 3
- Seo HreflangHreflang and international SEO — validate existing hreflang implementations (self-ref, return tags, x-default, language/region codes) and generate correct HTML/HTTP-header/sitemap implementations for multi-language and multi-region sites. Also audits cultural adaptation, content parity, locale formatting, and machine-translation quality across language versions.Votes: 0GitHub stars: 3
- Seo EcommerceE-commerce SEO — product-page on-page audit, Product schema (JSON-LD) requirements and scoring, Google Shopping / Amazon marketplace intelligence, organic-vs-Shopping keyword gaps, and UCP (Universal Commerce Protocol) agentic-checkout profile audit.Votes: 0GitHub stars: 3
- Seo Competitor PagesCompetitor comparison and alternatives pages — "X vs Y", "alternatives to X", "best [category] tools" roundups. Covers feature matrices, comparison-intent keyword targeting, Product/SoftwareApplication/ItemList schema, and conversion-optimized layout with fairness guidelines. A distinct page format, not the SERP-beating competitor analysis that feeds a regular article outline.Votes: 0GitHub stars: 3
- Market SizingMarket sizing — TAM/SAM/SOM built bottom-up from addressable accounts x realistic ACV, cross-checked against cited published figures, with every number sourced or marked [NEEDS DATA]. Use for "market sizing", "TAM", "SAM", "SOM", "how big is this market", "addressable market", "market opportunity", "is this market big enough", "size the opportunity", "total addressable market", "how much revenue is in this segment", "market size for the deck".Votes: 0GitHub stars: 3
- Content StrategyEditorial strategy — content pillars, the 60/30/10 calendar, format and channel mix, idea scoring, distribution (ORB), repurposing, and content audits. Use when the user asks "what should I write about", "content plan", "editorial calendar", "content pillars", "blog strategy", "content ideas", "content roadmap", "content audit", or "I don't know what to write". Owns the brand/editorial layer; keyword-driven cluster planning and article production belong to the SEO stack.Votes: 0GitHub stars: 3
- Out Of Order SectionsSYNTHETIC TEST FIXTURE, not a shipped skill: all nine required sections are PRESENT but Gotchas is written before Workflow, so only the section-ORDER check may fire against it.Votes: 0GitHub stars: 4
- Missing SectionSYNTHETIC TEST FIXTURE, not a shipped skill: identical to good-skill except that the Stop Conditions section is deliberately absent, proving the required-section presence check still fires.Votes: 0GitHub stars: 4
- Long DescriptionSYNTHETIC TEST FIXTURE, not a shipped skill: this description is deliberately padded past the 1024-character ceiling that validate-skills.py enforces on the strict-PARSED description value, so scripts/tests/test_validator.py can prove the parsed-length check still fires rather than merely asserting that it exists. The ceiling matters because external Agent-Skills consumers measure the parsed value and not the raw line: quoting characters and doubled apostrophes are serialization rather than c...Votes: 0GitHub stars: 4
- Thin ContractSummarizes changelogs. Use when a changelog needs a summary.Votes: 0GitHub stars: 4
- State ContradictorMaintains the project log file. Use when the log needs an entry.Votes: 0GitHub stars: 4