All authors

Claude Skills by greenfield-inc
github.com/greenfield-inc168 skills21 installs234 views
- Good Writing Fundamentals(foundational) The line-level rules for prose a person will read: active voice, concrete detail, direct verbs, and the AI patterns to cut. Applies to any prose before it ships. Use whenever prose is being written or edited, before it goes out: emails, blog posts, landing pages, docs, support replies, announcements, release notes, PR descriptions, README sections, or any text a person will read. Also use when asked whether writing sounds AI-generated. Runs as the gate at `seo-writing-framework...Votes: 0GitHub stars: 9
- HandoffPrepare a verified resumption brief when moving work to another agent, device, or session, including local-to-cloud coding handoffs. Use for "hand this off," "continue elsewhere," or "save where we are."Votes: 0GitHub stars: 9
- Html ExplainerThe house standard for any skill that renders an HTML page for a person to read, covering design tokens, typography, components, diagrams, and quality gates so every generated page shares one calm, graphic-first look. Use when a skill's instructions say to render its output per the html-explainer standards, or when the user asks for an HTML explainer of anything and no more specific skill applies.Votes: 0GitHub stars: 9
- ImplementExecutes an approved plan directly in Codex with one primary implementation stream by default, bounded sidecars only when write scopes are truly disjoint, and mandatory review gates for completeness and intent fidelity. Use after a plan is approved.Votes: 0GitHub stars: 9
- Implementation ReviewerReview completed code changes against a plan, run quality checks, and call out gaps, regressions, or missing integrations. Use when implementation work needs a plan-based review.Votes: 0GitHub stars: 9
- Pr Test AutomationRun first-pass automated manual testing for PRs that are reviewed or nearly ready to merge. Use when the user asks Codex to test a PR/branch/worktree, validate product flows, exercise browser or CLI workflows, map changed UI journeys with screenshots, verify analytics/webhooks/payments/email/SMS behavior through connected tools, or produce manual QA notes before human testing.Votes: 0GitHub stars: 9
- Prepare PrPrepare a branch for review by committing scoped changes, rebasing on main, running builds, and creating or updating a pull request. Use when the user wants the branch ready for PR review. Also use for rewriting an existing PR description from its current diff and evidence.Votes: 0GitHub stars: 9
- Principled ReviewSpawn 15 parallel review agents, each checking one code-quality principle with project-aware discovery.Votes: 0GitHub stars: 9
- Product CompareResearch a product category, compare options against requirements, and publish an interactive Grain comparison artifact with decision matrices, product images, feature checklists, day-in-the-life simulations, and hover previews. Use when the user wants to compare products for a purchase decision: 'compare X', 'help me pick a Y', 'what Z should I buy'.Votes: 0GitHub stars: 9
- RefactorPost-PR refactor pass. Sizes the diff against the remote default branch, fans out refactor-simple (and refactor-deep on large changes) as fresh subagents that run blind to each other, merges their plans once with max-severity rules, shows the merged report, and hands it to refactor-apply on the user's word. Use after a PR is open, or whenever the user asks to refactor or clean up the branch.Votes: 0GitHub stars: 9
- ReviewReview a PR against its linked issue, repository checks, correctness, architecture, and applicable conventions. Post structured findings as a PR review.Votes: 0GitHub stars: 9
- Seo Authority Pass(foundational) Add E-E-A-T signals: explainer pages, glossary, author attribution, structured data, OG images, and SEO metadata. Use when the user wants to improve SEO authority, add E-E-A-T signals, create explainer pages, add author attribution, or optimize metadata. Examples: 'add E-E-A-T', 'create explainer pages', 'add author bylines', 'SEO pass', 'add a glossary', 'authority pass', 'add structured data', 'create a what-is page'.Votes: 0GitHub stars: 9
- Seo Briefing(proactive) Pull analytics from PostHog, GSC, and Ahrefs. Correlate data and produce an actionable SEO briefing. Use when the user wants an SEO status report, morning briefing, analytics overview, or wants to understand how their site is performing. Examples: 'SEO briefing', 'how is the site doing', 'pull analytics', 'morning report', 'check indexing status', 'what keywords are we ranking for'.Votes: 0GitHub stars: 9
- Seo Content Drafting(execution) Create new SEO content: blog posts, landing pages, comparison pages based on the content strategy. Use when the user wants to create new content for SEO: blog posts, landing pages, comparison pages, or category pages. Usually follows seo-content-strategy. Examples: 'write the blog posts', 'create the landing pages', 'draft the comparison page', 'fill the content calendar'.Votes: 0GitHub stars: 9
- Seo Content Strategy(proactive) Turn an SEO briefing into a prioritized content plan: what to create, update, and index. Use when the user wants to decide what content to create or update based on data. Usually follows seo-briefing. Examples: 'what should we write', 'content strategy', 'what pages need work', 'plan the next batch of content', 'what keywords should we target'.Votes: 0GitHub stars: 9
- Seo Data Organize(support) Archive and organize .seo/ data into a dated wiki structure for historical tracking. This is a support skill that runs at the end of any SEO workflow. It archives the current .seo/ working data into a dated, browsable wiki structure so nothing gets lost and you can track SEO progress over time. Other SEO skills should call this as their final step.Votes: 0GitHub stars: 9
- Seo Data Pull(support) Discover connected analytics sources, pull data, write .seo/data/ snapshots, and visualize results with deltas vs prior pulls. This is a support skill. Don't invoke it directly. Other SEO skills (seo-briefing, seo-readability-pass, seo-authority-pass, seo-content-strategy, seo-content-drafting) call it as their first step when they need fresh data. If .seo/data/ is stale or missing, any SEO skill should run this first.Votes: 0GitHub stars: 9
- Seo Foundations(greenfield) Crawl your site, find competitors, map the search landscape, and build the starting point for all SEO work. Use when starting SEO from scratch, onboarding a new site, or when the agent doesn't know what the product is, who the competitors are, or what keywords matter. This is the zeroth step before seo-briefing. Examples: 'start SEO from scratch', 'set up SEO for this site', 'who are our competitors', 'what should we rank for', 'SEO foundations', 'greenfield SEO'.Votes: 0GitHub stars: 9
- Seo From CallsMine customer call transcripts (Doozy captures) for unmet search intents, validate against the existing site and competitive landscape, and draft the pages that fill the gaps. Use when the user wants to turn sales call insights into SEO pages: 'what pages should we create from today's calls', 'turn that call into pages', 'SEO from calls'.Votes: 0GitHub stars: 9
- Seo Readability Pass(foundational) Audit and rewrite website copy for voice consistency, readability, and first-timer comprehension. Use when the user wants to improve the readability, voice, or comprehension of product website copy. Examples: 'do a readability pass', 'fix the copy', 'rewrite the docs to match my voice', 'the docs sound too technical', 'do a comprehension audit', 'humanity pass on the website'.Votes: 0GitHub stars: 9
- Seo Writing Framework(foundational) Research, draft, reader-hat, edit, slop-gate, score process for any customer-facing deliverable. Use when producing any customer-facing deliverable: pricing emails, blog posts, landing pages, docs, support replies, announcements, PR descriptions, onboarding copy, or any writing where the words matter. Can be invoked standalone or called by other SEO skills (readability, authority, drafting) as their writing process. Examples: 'write this email', 'draft this announcement', 'help...Votes: 0GitHub stars: 9
- Session TracePublish an agent session as a readable trace page in Grain, with the story, key moments, every request and step on a timeline, subagents, and the pull requests it opened. Use when asked for a trace or "how did this run go", or when a task already has a Grain page (for example from prepare-pr or handoff).Votes: 0GitHub stars: 9
- Simple PlanQuick gut-check before implementing when the user directly asks you to do something. Investigates, proposes a lightweight plan, and implements only after approval. Use this instead of `create-plan` when the change is straightforward.Votes: 0GitHub stars: 9
- Tech Deep DiveResearch an emerging technology, product capability, or workflow from X, Reddit, demos, documentation, and source code; explain its reusable mechanisms, practical applications, and experiments in a visual field guide. Use for technology deep dives and surprising use cases, including updating an existing Grain.Votes: 0GitHub stars: 9
- Ui MockupCreate three UI mockup options per round from product screenshots, then refine the user’s favorite. Use for "mock this up," "UI mockup," or "show me what this would look like" for interfaces. Collect screenshots and save approved designs with the ticket or brief.Votes: 0GitHub stars: 9
- Ui OptionsWhen the person dislikes how a piece of UI looks (often mid-QA), build three real design options in the actual code, screenshot each in the same set of states and contexts, open the folder in Finder, recommend one, then land the chosen option. Use for "I don't like this UI", "this looks off / not modern / cluttered", or "give me options for X" about an existing screen. For new screens that do not exist yet, use ui-mockup.Votes: 0GitHub stars: 9
- Babysit PrUse after a pull request is open to watch its CI and review-bot comments until it is ready. Fixes real findings, replies with a reason to false positives, rebases when the base moves, and stops when bots and required checks are green. Merges only when the person asked.Votes: 0GitHub stars: 9
- BriefUse when a problem, idea, or change of intent is worth capturing, or the person asks to write it up or file an issue. Never chooses a solution.Votes: 0GitHub stars: 9
- Bug IntakeUse when the person reports broken behaviour or starts a session to file a bug. Reproduces and reports. Never fixes.Votes: 0GitHub stars: 9
- ExplainUse when the person wants to understand a concept or how something works today. Never plans.Votes: 0GitHub stars: 9
- OptionsUse when the person asks what to do or for trade-offs, or more than one design is live. Waits for a pick. Never plans.Votes: 0GitHub stars: 9
- Orchestrate SessionsCoordinate authorized work through host-managed workspaces and planner, implementer and reviewer sessions, keep the workstream map, watch in-flight work, and clean up finished worktrees, without taking over the workers' work.Votes: 0GitHub stars: 9
- PlanUse when the direction is chosen and the person wants a plan. Writes a high-level HTML cover sheet with package outcomes and explicit validation criteria. Never implements.Votes: 0GitHub stars: 9
- Session TracePublish agent sessions as readable trace pages in the workspace's document destination, with the story, key moments, every request and step on a timeline, subagents, and the pull requests it opened. Use when asked for a trace or "how did this run go", when a task already has a published page (for example from prepare-pr or handoff), or when an orchestrator collects the traces of a Session.Votes: 0GitHub stars: 9
- SpikeUse only when a decision is blocked on a fact nobody has. One time-boxed question, one answer.Votes: 0GitHub stars: 9
- Verify AppUse when behaviour must be proven in the running application: journeys, screenshots for visual checks, external effects, or reproducing a bug. Never fixes.Votes: 0GitHub stars: 9
- ArenaCompare independent drafts and combine their strongest ideas when an artifact's structure is still unsettled.Votes: 0GitHub stars: 9
- Backend VerifierBackend-verifier role in an automated development pipeline: proves backend verification criteria by running the mapped tests, scripts, and commands with quoted evidence. Use when dispatched to verify implemented work.Votes: 0GitHub stars: 9
- Code ResearcherCode-researcher role in an automated development pipeline: explores the codebase and returns current-state facts with precise file:line references. Use when dispatched to answer a question about what exists in the repo.Votes: 0GitHub stars: 9
- Code ReviewerCode-reviewer role in an automated development pipeline: reviews the diff for correctness and security with file:line evidence. Use when dispatched to review an implementation.Votes: 0GitHub stars: 9
- Codex DoRun the full autonomous pipeline against a work item - plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a work-item reference (issue #/URL in whatever tracker the repo's AGENTS.md configures) or a local ./tmp/<id>/brief.html produced by /create-brief.Votes: 0GitHub stars: 9
- Codex HillclimbImprove one measurable metric toward a target through controlled experiments, retaining only verified gains.Votes: 0GitHub stars: 9
- Codex InvestigateInvestigate broken behavior using the shared evidence-driven method, scaling from a normal root-cause pass to a deep falsifiable experiment loop.Votes: 0GitHub stars: 9
- Codex Security ScanRun or diagnose an authorized repository scan with the official Codex Security plugin, applying repository-specific scope and reporting policy when present. Use for explicit security scans, scheduled scan runs, or Codex Security preflight failures; not for ordinary code review.Votes: 0GitHub stars: 9
- CodexDispatches one Codex (GPT-6.1 Sol) sub-agent via `codex exec` - implementer, backend-verifier, plan-reviewer, code-reviewer, code-researcher, or investigator - and returns its report. Used by /do, /discussion, and /create-brief whenever one of these roles runs; not normally invoked by the user directly. Use when a pipeline stage needs its Codex sub-agent dispatched, resumed for a fix round, or re-run.Votes: 0GitHub stars: 9
- Cold ReadGive a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process, instructions, code. It reports what's broken, confusing, or contradictory. A fresh perspective on something before it ships - especially useful on a PR you think is finished, or any user-facing artifact. Always dispatch as a fresh sub-agent with no conversation history - the zero context is the point.Votes: 0GitHub stars: 9
- Create BriefCapture converged work as one or more briefs ready for /do, or revise an existing brief as accepted intent changes. Use for requested work-item capture, concrete follow-ups, and agreed revisions during discussion. Supports features, multi-phase changes, and investigated bugs; exploratory ideas remain in discussion.Votes: 0GitHub stars: 9
- DiscussionInteractive back-and-forth to clarify, understand, or figure something out - an idea, an approach, a tradeoff, or a suspected bug. Use when the user wants to think out loud or explore before committing to anything - e.g. "let's discuss X", "help me understand Y", "why is Z happening", "what should we do about W". Produces clarity plus a dated decision log, not deliverables; work items are created afterward with /create-brief.Votes: 0GitHub stars: 9
- DoRun the full autonomous pipeline against a work item - plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a work-item reference (issue #/URL in whatever tracker the repo's AGENTS.md configures) or a local ./tmp/<id>/brief.html produced by /create-brief.Votes: 0GitHub stars: 9
- Excalidraw Pr DiagramsCreate Excalidraw diagram JSON files and PR visual overviews that make visual arguments. Use when the user wants to visualize workflows, architectures, concepts, pull request changes, before/after behavior, or a shareable explainer image for reviewers.Votes: 0GitHub stars: 9