Agent skills I use for SEO, growth, and agent-operations work that needs evidence, execution, verification, and memory — not one-shot audits or slide-deck recommendations.
Real growth work is hard. One-shot prompts produce generic checklists. Framework-heavy workflows try to own the process, but they often bury the business context and make it hard to tell what actually shipped. These skills stay small, composable, and adaptable. They work with any model. Hack around with them. Make them your own.
- Run the skills.sh installer:
npx skills@latest add JorgeMenaDev/skills-
Pick the skills you want and which coding agents to install them on.
-
Open a session in a target repo and invoke the skill that matches the work — for example, start SEO work with
seo-growth-workspace.
Most people begin with seo-growth-workspace. For unattended multi-phase shipping, add shiploop. When the question is where a plan should live, use work-tracking. To publish through Andy MCP, add andy-post.
A job-file handoff protocol between a requesting agent and the Operator — a human-supervised computer-use agent on a real desktop/browser. Jobs, reports, and evidence live in .agents/operator/; a per-repo HOST.md carries the machine-, account-, and repo-specific facts so the skill itself stays portable.
Use it when a task needs real clicks or credentials the agent doesn't hold: desktop app setup, third-party dashboards, OAuth consents, captchas, 2FA, Gherkin QA runs, or delegated implementation of fully-designed code slices.
npx skills@latest add JorgeMenaDev/skills --skill operator-handoffA two-vendor adversarial review protocol for hard-to-reverse architecture or design decisions. Two flagship reviewers from different vendors attack a file-backed proposal in parallel; the chair synthesizes, revises, and re-convenes for up to three rounds. A one-vendor run is a second opinion, not counsel. Runtime launch adapters stay consumer-local (e.g. Claude Code .claude/skills/counsel/).
npx skills@latest add JorgeMenaDev/skills --skill counselA system-first review loop for external articles, videos, repositories, prompts, and tactics. It captures the material claims in temporary scratch space, compares them with the user's existing systems, selects one owned improvement or no change, and stops for approval before durable workspace or external-system mutation.
npx skills@latest add JorgeMenaDev/skills --skill source-to-systemDraft and publish social posts through Andy MCP. The operator gives a raw idea. The agent returns 2-3 drafts. After a pick, it publishes or schedules. Andy MCP is an active build: file skill or MCP friction on this repo.
npx skills@latest add JorgeMenaDev/skills --skill andy-postAn isolated deep-research loop over native xAI Grok Build CLI. It defaults to native web search, can expose only Firecrawl MCP when requested, audits evidence gaps in one temporary session, and emits a consistently structured cited report plus provider-usage metadata.
npx skills@latest add JorgeMenaDev/skills --skill grok-deep-researchI built these skills to fix failure modes I keep seeing in AI growth and agent-ops work.
"No-one knows exactly what they want."
David Thomas & Andrew Hunt, The Pragmatic Programmer
The problem. The internet already has enough SEO checklists. The useful work is deciding what matters for this business, this repo, this market, and this moment. Most agents skip that and optimize pages without understanding the business.
The fix is seo-growth-workspace — gather context, inspect live and code evidence, and turn findings into a prioritized backlog instead of stopping at recommendations.
Example: recommendation vs ticket
- Before: "Improve meta descriptions across the blog."
- After: A
.seo/backlog.mdticket — target URL, rendered title/description evidence, business intent, one verification step, and a handoff note in.seo/log.md.
The problem. SEO compounds only when the next pass can trust the previous one. Without durable notes, agents re-audit the same surfaces, forget blockers, and repeat work that already failed.
The fix is a predictable workspace. seo-growth-workspace bootstraps .seo/ — context, backlog, audit evidence, reports, backlinks, decisions, and handoffs in files the next agent can find. work-tracking applies the same idea when the question is broader: repo markdown, GitHub Issues, Linear, or memory.
"Always take small, deliberate steps. The rate of feedback is your speed limit."
David Thomas & Andrew Hunt, The Pragmatic Programmer
The problem. A content plan is not done because the calendar looks nice. A technical fix is not done because code changed. A backlink is not live because it was submitted.
The fix is verification built into the loop: live URLs, rendered metadata, sitemap state, Search Console evidence, analytics proof, UI checks, or public links. Every action pushes toward proof, not paperwork.
The problem. Growth agents love opening five lanes at once — audit, content, schema, backlinks, reporting — and finishing none of them. Unattended runs die when context resets. Incidents get "fixed" without a durable record.
The fix is one current focus ticket, clear done criteria, and skills for the heavy lifts:
seo-growth-workspace— one high-leverage SEO action per pass, with handoff.shiploop— multi-phase shipping through GitHub issue ledgers, gated PRs, and worker adapters when the run must survive context loss.
Growth fundamentals matter more than ever: context before advice, memory between sessions, proof before "done," and one focus at a time. These skills condense that into repeatable operating loops for SEO work, plan tracking, autonomous shipping, and production incidents.
All skills below are model-invoked — the agent can reach for them when the task fits, or you can invoke them directly.
- seo-growth-workspace — Durable SEO operating workspace: bootstrap
.seo/, capture business context, audit evidence, prioritize backlog, implement one action, verify live, log handoff. Technical SEO, Search Console, schema, local SEO, content ops, internal links, backlinks, pSEO, conversion paths, monthly reporting. - andy-post — Draft and publish X, LinkedIn, and Instagram posts through Andy MCP: raw idea → 2-3 drafts → operator picks → publish or schedule.
- posthog-growth-workspace — Durable product-data growth workspace on live PostHog data: bootstrap
.growth/, funnels/activation/retention, experiment and campaign registries, session-replay mining, HogQL cookbook + query runner, monthly growth reviews. Sibling ofseo-growth-workspace— SEO stays there; install doctrine stays with your stack.
- operator-handoff — Job-file handoff between a requesting agent and a human-supervised computer-use Operator: jobs, reports, evidence trails, and a per-repo
HOST.mdhost profile. - orchestrate — Conduct multi-agent work from a human-readable plan or a GitHub-autopilot spec: capability-aware frontier dispatch, isolated ticket PRs, conductor review gates, and verified integration.
- crew-dispatch — Crew-first task dispatch with a durable
crew/<id>/record, plus detached completion supervision: the crew reports its terminal status and wakes its supervisor after the launching turn ends (T3/Codex runtime reference included). - source-to-system — Turn external material into one evidence-backed, owned system improvement or an explicit no-change decision.
- grok-deep-research — Run isolated, bounded Grok research with native or Firecrawl search and produce a stable cited report plus an iteration ledger.
- mobile-monorepo-ios — Build, debug, and release Expo/React Native, native iOS, native Android, or bounded hybrid mobile work through explicit architecture, release-system, device, and distribution proof contracts.
- design-system-keeper — Extract, encode, and enforce a repo's real design system as an agent-readable canon (v0 Design Systems 2.0 shape): sourced rules, a primitive index, verify-against-source builds, and a drift backlog instead of memory-built lookalikes.
- cursor-subagent — Cursor sidecar delegation for explicit Cursor/Grok exploration, review, or isolated implementation.
- using-git-worktrees — Storage-aware development lifecycle: source-only task workspaces, bounded hydration, reusable local-main runtimes, isolated local state, automatic dehydrate, and reviewed retirement.
- work-tracking — Decide where multi-step work should live: repo markdown, GitHub Issues, Linear, memory, or a mix. When to promote tasks to issues and how future agents find current state.
- sync-github-fork — Confirm a GitHub fork's parent, measure divergence, and integrate upstream changes into its published default branch without rewriting fork history.
- product-feedback-report — Create resumable founder-led feedback reports for web and mobile products, with conversational capture, screenshot/video evidence, automatic prioritization, and an always-current PDF.
- visual-plan — Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful. Agent-Native visual planning, portable across hosted, self-hosted, and local-files modes.
- shiploop — Turn a plan, fix, or feature into an unattended shipping run: GitHub issue ledger, dependency-gated phases, gated PRs, review evidence, optional worker adapters.
fixloop— deprecated 2026-07-05 (history): incident debugging now = Sentry evidence +STACK.mdhandles (Matias profile) + thediagnosing-bugsskill (github.com/mattpocock/skills) + per-repoAGENTS.mddebugging notes.
cursor-subagent source lives in skills/software-development/cursor-subagent/. Update it there first, bump version: in SKILL.md, commit and push JorgeMenaDev/skills, then update consumers such as Matias with:
cd ~/.hermes/profiles/matias
npx skills@latest update cursor-subagent -p -yPublic page: https://www.skills.sh/jorgemenadev/skills/cursor-subagent