Loading...
Loading...
Found 86 Skills
Session log provenance tracking. TRIGGERS - who created, trace origin, session archaeology, ADR reference.
Use when understanding legacy or undocumented systems, creating documentation for existing code, or extracting specifications from implementations. Invoke for legacy analysis, code archaeology, undocumented features.
How to design a content hub that earns topical authority. Pillar topic selection, cluster planning, internal linking architecture, URL structure, pillar and cluster page anatomy, topical authority signals for SEO and AEO/GEO, and the maintenance discipline that distinguishes intentional hubs from accidental orphans. Triggers on pillar content, content hub, topic cluster, topical authority, content architecture, hub and spoke, pillar page, cluster page, content silo, internal linking strategy. Also triggers when a content set is not ranking despite individual piece quality, when a pillar was launched without a cluster, or when content has accumulated without an architecture.
Stage 2 (REX mode only) — Git archaeology, changelog analysis, verified factual timeline. Skip automatically in Concept mode.
Use this skill when performing keyword research, search intent analysis, keyword clustering, SERP analysis, competitor keyword gaps, long-tail keyword discovery, or evaluating keywords for snippet opportunity, AI Overview presence, and tri-surface keyword reports. Covers organic (SEO), answer engine (AEO snippets/PAA), and AI citation (GEO AI Overviews/ChatGPT Search/Perplexity) surfaces.
This spell is archaeology, not history research. It operates on specific artifacts from a specific dead system to answer specific questions. It is NOT general tech history, NOT interviewing living people, and NOT monitoring live systems.
Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) strategies for AI-powered search visibility in ChatGPT, Perplexity, Google AI Overviews, and other AI search platforms. Use when working with aeo, geo, ai search, chatgpt search, perplexity, ai overviews, generative search, llm visibility.
Two-way traceability between commits and tickets. (A) When committing any change, make sure the commit message carries the ticket / work-item number — derive it from the user's words, the branch name, or the current task, ask if unknown (a commit-msg hook is bundled but install it only on explicit request). (B) When the user asks WHY code is the way it is — "why was this changed", "who decided this", "is this hardcode intentional", "ทำไมถึงแก้อันนี้", "มีเหตุผลป่าว" — trace the line through git blame/log to the commit, extract the ticket number from the message, fetch the ticket from the tracker (Azure DevOps, GitHub Issues, JIRA), INCLUDING downloading and reading attached images (requirements often live only in an annotated screenshot), and answer with commit + ticket evidence. Trigger on any commit request in a ticketed repo, on "install commit hook", and on any why-is-this-code-like-this / change-archaeology question — even when the user doesn't mention tickets.
SurgeGraph is the Answer Engine Optimization (AEO) platform that tracks AI citations, scores pages for citation readiness, and one-click fixes the gaps — now every workflow runs from the terminal or any agent. Trigger phrases: `what changed in SurgeGraph this week`, `AI Visibility for my project`, `which prompts lost AI citations`, `publish gap articles from a topic research`, `what knowledge libraries actually show up in citations`, `use surgegraph`, `run surgegraph`.
Create marketing content organized by funnel stage with content strategy, distribution plans, and SEO/AEO strategy. Use when the user says "content strategy", "marketing content", "blog post", "case study", "social posts", "content calendar", "SEO strategy", or needs to create content that drives pipeline.
Runs the demand side of an SEO and AEO program in two modes. Topic pipeline pulls live keyword and prompt volumes with real numbers, builds an answer-engine question map, and writes a writer content brief. Monitoring watches Search Console and prompt visibility and reports only state changes. Binds each job to whatever research and chat tools the team already has instead of requiring a named vendor. Use when asked to "what's the search volume", "check prompt volume", "write a content brief", "brief this article for a writer", "build a question map", "what questions should this page answer", "review Search Console", "why did our clicks drop", or "set up SEO monitoring". Writes briefs and research, never the article itself. For implementing the page in code use optimise-seo, and for the article use the external ghostwriter skill with platform blog.
Use this skill for complex git operations including rebases, merge conflict resolution, cherry-picking, branch management, or repository archaeology. Activates on mentions of git rebase, merge conflict, cherry-pick, git history, branch cleanup, git bisect, worktree, force push, or complex git operations.