ワンクリックで
seo-data-organize
(support) Archive and organize .seo/ data into a dated wiki structure for historical tracking.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
(support) Archive and organize .seo/ data into a dated wiki structure for historical tracking.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run the full autonomous pipeline against a work item — plan, implement, verify, PR, post-PR review + QA, wrap-up. Takes a GitHub issue
The Notion bridge for work items — creates a Notion work item mirroring a GitHub issue, uploads artifacts (item.md, refs/, plan.md, wrapup.md) to it, and pulls a work item's artifacts down to ./tmp/<id>/. Used by /create-feature, /create-epic, /create-issue (publish) and /do (pull before work, upload after). Use when a work item needs to be published to, updated in, or fetched from Notion.
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.
Dispatches one Codex (GPT-5.6) 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-issue 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.
Captures a discussed multi-phase workstream as an Epic Spec work item ready for /do. For a single-outcome change use /create-feature instead.
Captures a discussed feature as a lean Feature Ticket work item ready for /do. For multi-phase workstreams use /create-epic instead.
| name | seo-data-organize |
| description | (support) Archive and organize .seo/ data into a dated wiki structure for historical tracking. |
| allowed-tools | ["Read","Write","Bash"] |
| when_to_use | 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. |
| model | claude-opus-4-6 |
Archive and organize .seo/ working data into a dated, browsable wiki
structure. Runs at the end of any SEO workflow so data accumulates into a
searchable history instead of getting overwritten.
This is a support skill. Other skills call it as their final step.
Over time, .seo/ becomes a self-organized wiki of SEO data:
.seo/
data/ # current working data (from seo-data-pull)
manifest.md
analytics.md
search-console.md
seo-tool.md
briefing.md # current working briefing
strategy.md # current working strategy
archive/ # dated snapshots (this skill creates these)
2026/
06/
24/
briefing.md
strategy.md
data/
manifest.md
analytics.md
search-console.md
seo-tool.md
10/
briefing.md
...
05/
27/
briefing.md
...
experiments/ # tracked experiments
2026-06-24-windows-landing-page.md
2026-06-10-remote-pane-blog-post.md
index.md # auto-generated table of contents
If .seo/briefing.md or .seo/strategy.md exist:
.seo/archive/YYYY/MM/DD/briefing.md, strategy.md, and data/* into the archiveSuccess criteria: Today's data is preserved in the archive. Working files still exist.
Scan the current strategy and any PRs merged since the last organize run. For each new piece of content created or significant change made:
.seo/experiments/YYYY-MM-DD-short-name.mdExperiment files use this format:
# [Short name]
- **Date**: YYYY-MM-DD
- **Type**: new page / rewrite / E-E-A-T / blog post
- **Target**: [keyword or metric]
- **Baseline**: [data from briefing at time of creation]
- **Action**: [what was done]
- **Strategy ref**: [link to .seo/archive/YYYY/MM/DD/strategy.md]
## Follow-ups
- YYYY-MM-DD: [updated data, outcome so far]
Success criteria: Every content action from this cycle has an experiment file.
Regenerate .seo/index.md as a table of contents:
# SEO Data Index
## Latest
- [Current briefing](briefing.md) — YYYY-MM-DD
- [Current strategy](strategy.md) — YYYY-MM-DD
## Archive
- [2026-06-24](archive/2026/06/24/) — briefing, strategy, data
- [2026-06-10](archive/2026/06/10/) — briefing, strategy
- ...
## Active Experiments
- [windows-landing-page](experiments/2026-06-24-windows-landing-page.md) — tracking
- [remote-pane-blog-post](experiments/2026-06-10-remote-pane-blog-post.md) — tracking
- ...
## Data Sources
- [Current manifest](data/manifest.md) — what's connected
Success criteria: .seo/index.md is up to date and links to everything.
If working files in .seo/ are older than 7 days and have been archived,
note them as stale in the index. Don't delete them automatically.
Success criteria: Stale data is flagged but not destroyed.