dcouple
@dcouple Organization
Public Skills
create-ticket
by dcouple
Capture work and evolving intent during discussion as one or more GitHub tickets, Grain briefs, or both. Use for ticket or issue creation, follow-ups, backlog capture, delegation, and revisions as decisions change. Preserve the what, why, outcome, scope, and acceptance criteria.
prepare-pr
by dcouple
Prepare 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.
seo-content-drafting
by dcouple
"(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'."
seo-authority-pass
by dcouple
"(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'."
seo-briefing
by dcouple
"(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'."
seo-content-strategy
by dcouple
"(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'."
good-writing-fundamentals
by dcouple
"(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 step 5, and standalone on any existing draft. Examples: 'write this email', 'clean up this draft', 'does this sound like AI', 'make this sound like a person wrote it', 'edit this before I send it'. Not for code, identifiers, logs, or config."
seo-foundations
by dcouple
"(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'."
seo-data-organize
by dcouple
"(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."
astra-ticket
by dcouple
Take a GitHub ticket through Astra planning, Luna implementation, PR creation, optional Sol QA, Luna/Astra reviews, and bounded QA revalidation.
excalidraw-diagram
by dcouple
Create 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.
seo-data-pull
by dcouple
"(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."
seo-writing-framework
by dcouple
"(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 me write this', 'writing framework', 'apply the writing process'."
seo-readability-pass
by dcouple
"(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'."
plan-reviewer
by dcouple
Review an implementation plan for repo accuracy, fact purity, intent fidelity, reconciliation quality, and completeness. Use when a plan needs a correctness and completeness pass.
create-plan
by dcouple
Creates a reconciled implementation plan by combining a structured plan draft with a normalized intent brief and a PRP-style research dossier, then auto-reviews the final plan. Use when planning a new feature or significant change in Codex.
planner-proof
by dcouple
Report the unique Orchestra test marker when explicitly requested.
codebase-explorer
by dcouple
Explore the notetake codebase to locate files, trace behavior, and document existing patterns with precise file references. Use when the task is understanding what exists, not proposing changes.
worker-proof
by dcouple
Report the unique Orchestra test marker when explicitly requested.
explain-visually
by dcouple
Complement an answer or discussion with a first-principles visual HTML explanation, saved in Grain when connected. Use when explaining how something works, why it changes, or how options differ and a visual would materially help understanding, including requests like "show me" or "help me understand." Skip simple factual answers and text-only requests.
investigate
by dcouple
Investigate a bug or broken behavior through hypothesis-driven root cause analysis and report what is wrong without jumping straight to a fix. Use when something is failing or behaving unexpectedly.
implementation-reviewer
by dcouple
Review 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.
pr-test-automation
by dcouple
Run 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.
cold-read
by dcouple
Give 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.