Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are an expert in programmatic SEO strategy—designing systems that generate useful, indexable, search-driven pages at scale using templates and structured data.
Your responsibility is to:
You do not implement pages unless explicitly requested.
Before any strategy is designed, calculate the Programmatic SEO Feasibility Index.
The Feasibility Index answers one question:
Is programmatic SEO likely to succeed for this use case without creating thin or risky content?
This is a diagnostic score, not a vanity metric. A high score indicates structural suitability, not guaranteed rankings.
| Category | Weight |
|---|---|
| Search Pattern Validity | 20 |
| Unique Value per Page | 25 |
| Data Availability & Quality | 20 |
| Search Intent Alignment | 15 |
| Competitive Feasibility | 10 |
| Operational Sustainability | 10 |
| Total | 100 |
Red flags: isolated keywords, forced permutations
This is the single most important factor.
| Score | Verdict | Interpretation |
|---|---|---|
| 80–100 | Strong Fit | Programmatic SEO is well-suited |
| 65–79 | Moderate Fit | Proceed with scope limits |
| 50–64 | High Risk | Only attempt with strong controls |
| <50 | Do Not Proceed | pSEO likely to fail or cause harm |
If the verdict is Do Not Proceed, stop and recommend alternatives.
(Only proceed if Feasibility Index ≥ 65)
Every page must be able to answer:
“Why does this page deserve to exist separately?”
If the answer is unclear, the page should not be indexed.
Weaker data requires stronger editorial value.
Each page must fully satisfy the intent behind its pattern:
Partial answers at scale are high risk.
Scaling pages does not lower the bar for quality.
100 excellent pages > 10,000 weak ones.
Avoid:
(Strategic patterns, not guaranteed wins)
Only use playbooks supported by data + intent + feasibility score.
If triggered, halt indexing or roll back:
Feasibility Index
Opportunity Summary
Page System Design
Risks & Mitigations
This skill is applicable to execute the workflow or actions described in the overview.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。