Claude Skills by benjaminthomas

github.com/benjaminthomas

8 skillsA× 80 installs0 views

Generative SeoARun an evidence-based SEO + GEO (Generative Engine Optimization) program for ANY website or product codebase — auditing technical SEO, writing or retrofitting content so it gets cited by ChatGPT/Perplexity/AI Overviews, tracking AI-citation visibility, refreshing competitor research, and drafting distribution posts. Use whenever the user asks to audit SEO, improve AI-search/AI-citation visibility, write or optimize marketing/blog content for search or GEO, check whether a product shows up in ...ai-agentsgonextjsVotes: 0GitHub stars: 2
Spec CheckpointACreate a comprehensive checkpoint commit with detailed analysis of all changes. Use this skill when the user says "checkpoint", "commit everything", "save my progress", "create a commit", or wants to stage and commit all current changes with a well-crafted message. Also use when the user says "/spec-checkpoint" (or their host's equivalent invocation syntax) or asks to snapshot current work. This skill stages all changes and creates a descriptive commit — it does not push.ai-agentsgobashVotes: 0GitHub stars: 2
Spec CreateACreate a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture decisions as actionable spec files. Also use when the user says "/spec-create" (or their host's equivalent invocation syntax) or wants to decompose a feature into work items that age...ai-agentsgotestingVotes: 0GitHub stars: 2
Spec ImplementAOrchestrate parallel implementation of a feature specification by dispatching coder agents batch-by-batch with code review gates between batches. Use this skill when the user says "implement this feature", "start implementing", "run the spec", "execute the plan", "continue implementing", "approved, run it through", or wants to begin coding a previously planned feature from a specs/{feature}/ folder. Also use when the user says "/spec-implement" (or their host's equivalent invocation syntax) o...ai-agentsgogitVotes: 0GitHub stars: 2
Spec InvestigateADeep, evidence-based technical investigation of a piece of work BEFORE any specification or implementation begins — starting from a ticket (Jira, GitHub Issues, Linear), a meeting/call transcript, a plain-text description, a doc/PRD file, a Slack/email thread, or an error log. Use when the user says "investigate STP-123", "spec-investigate", "look into this before we plan it", or hands over any of those inputs and wants the system understood (current behaviour, root cause, affected repos/file...ai-agentsgotestingVotes: 0GitHub stars: 2
Spec SetupAOne-time discovery that teaches the spec-driven-dev pipeline how THIS project works, and saves the answers to .spec-driven.yml — project layout (single repo, monorepo, or multiple repos), issue tracker, base branch, PR target, branch naming, commit style, and the lint/typecheck/test/ build/dev commands. Use when the user says "set up spec-driven", "configure the pipeline", "spec-setup", "change our branch rules", or when any other spec-* skill finds no .spec-driven.yml. Detects everything it ...ai-agentsgogitVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Spec ShipAPush the current branch to GitHub and create a pull request. Use this skill when the user says "ship it", "ship this", "push to github", "create a pr", "open a pull request", "send for review", "get this reviewed", or wants to push their work and open a PR. Also use when the user says "/spec-ship" (or their host's equivalent invocation syntax). This skill handles prerequisites, branching, pushing, and PR creation — it does not commit or run quality checks (use spec-checkpoint for that first).ai-agentsbashgitVotes: 0GitHub stars: 2
Spec VerifyAVerify a completed feature spec by driving the real running app — not just lint/typecheck/build — and checking off every acceptance criterion from its specs/{feature}/ folder one by one. Use this after /spec-implement finishes a spec, when the user says "test this end to end", "verify this feature actually works", "did we actually build this right", or "/spec-verify", and before /spec-ship or opening a PR. This is the spec-aware sibling of the generic /verify and /run skills — /verify checks ...ai-agentsrustgoVotes: 0GitHub stars: 2