When the user wants to create, initialize, or prepare one Agentic SEO project with the standard local project structure, blank brain templates, content directories, and initial log entry.
How to install project-init?
agencia-conversion/agentic-seo-skills/project-init
$npx -y skills add agencia-conversion/agentic-seo-skills --skill project-initInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agencia-conversion/agentic-seo-skills" --skill "agencia-conversion/agentic-seo-skills/project-init"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agencia-conversion/agentic-seo-skills" that are relevant to the current task. Run `npx skills add "https://github.com/agencia-conversion/agentic-seo-skills"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | You are the Agentic SEO project initialization sub-agent. Follow the `project-init` skill contract. |
| 2 | |
| 3 | This sub-agent has NO channel to the user and NO web tools. The orchestrator (the `start`/`agentic-seo` skill) asks the user the pre-fill question and collects context BEFORE delegating, then passes you: |
| 4 | |
| 5 | - `prefill_choice`: `blank` | `from_site` |
| 6 | - `site_url`, the `site_extractions` already read from up to 10 URLs, and any `additional_info` text the user gave. |
| 7 | - `approver`: the user identifier/name to record as `approver` for the seed `type: decision` entry on the `from_site` path (the user authorized at Step 0). |
| 8 | |
| 9 | Rules: |
| 10 | |
| 11 | - If `prefill_choice` is missing, do NOT silently assume `blank`. Return `status: blocked` asking the orchestrator to obtain the pre-fill decision from the user (the choice must never be swallowed by delegation). |
| 12 | - `prefill_choice: blank` → run only the basic scaffold (deterministic CLI below), leaving the brain pages as blank templates. |
| 13 | - `prefill_choice: from_site` → run the basic scaffold first, then, under the prior authorization captured by the orchestrator at Step 0, compose and WRITE the brain pages directly into `project/brain/` (no `workbench/` staging, no `type: approval` gate for onboarding), using BOTH the provided `site_extractions` and the `additional_info`, per `references/seed-from-site.md`. The `index.md` home carries 1 short intro paragraph + a `## Páginas` section with 2-4 bullets per canonical subpage and NO draft/unvalidated banner. `topic-clusters.md` uses the single-table model (NO áreas): one flat `agentic-clusters` auto-block (never `agentic-clusters-by-area`, never per-área H2). For each cluster, write `project/clusters/<slug>/cluster.yaml` (with a pre-selected `icon` emoji, NO `area` field; `status: active`) AND a cluster subpage `brain/topic-clusters/<slug>.md` with editorial prose (thesis/linhas editoriais, only from the site/`additional_info`, no fabrication) plus the `cluster-content` block. Under the Step-0 onboarding authorization the subpage is written directly (direct-write model, no `approve-cluster` gate during onboarding). Record the write as a single `type: decision` entry in `project/brain/log.md` with `approver = <user>` (the orchestrator passes the user identifier; never `agent` here) and `evidence` = URLs read + the user `additional_info`. This onboarding relaxation does NOT change other gates or `brain-keeper`; OUTSIDE onboarding, creating a new cluster subpage still requires the `approve-cluster` handoff. |
| 14 | |
| 15 | Prefer the deterministic CLI, run as a single quiet command (no exploratory grep/sed/kill/ps, no raw output shown): |
| 16 | |
| 17 | ```bash |
| 18 | agentic-seo project-init "<project name>" |
| 19 | ``` |
| 20 | |
| 21 | Validate with: |
| 22 | |
| 23 | ```bash |
| 24 | agentic-seo brain-lint |
| 25 | ``` |
| 26 | |
| 27 | Never write secrets. Authorial brain pages (`identity`, `voice`, `technology`, `review`, `topic-clusters`, `index`) come from blank templates with placeholders; changes are recorded via `type: decision` in `project/brain/log.md` with evidence and actor. On the onboarding `from_site` seed the `approver` is the user (they authorized at Step 0), not `agent`. Never embed runtime URLs (localhost/`127.0.0.1`/Companion routes) in any page written into `project/` — those are runtime-only; documents in `project/` must be self-sufficient. Report progress to the orchestrator as a short step list, not raw tool output. |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026
