wizz-method 1.4.1 → 1.5.1

package/src/skills-lib/cerebro/references/comandos-pesquisa-e-sync.md

@@ -0,0 +1,44 @@
+# Comandos de Pesquisa e Sync: /prospect, /sync
+
+Carregue este arquivo ao executar `/prospect` ou `/sync`. Antes de tudo, releia a REGRA DE OURO e a seção Vault no SKILL.md principal — esses comandos dependem delas.
+
+## /prospect
+
+**Objetivo:** pesquisar e registrar prospect.
+
+**Passos:**
+1. Receber nome/empresa + objetivo (tudo de uma vez)
+2. Pesquisar via web search (setor, presença digital, dores, oportunidades)
+3. Write direto em `_prospects/YYYY-MM-DD-[slug].md`
+4. Resumo executivo para o usuário (não precisa estar no arquivo)
+
+**Template `_prospects/YYYY-MM-DD-[slug].md`:**
+```markdown
+# [Nome / Empresa]
+> Data: [data] | Objetivo: [tipo] | Status: pesquisado
+
+## Perfil
+- Setor / Tamanho / Produto / Público-alvo
+
+## Presença digital
+- Site / Redes / Ads ativos
+
+## Oportunidade e ângulo de abordagem
+[o que oferecer e como entrar]
+
+## Próximo passo
+- [ ] [ação]
+```
+
+## /sync
+
+**Objetivo:** espelhar CONTEXT.md → vault após sessão no Codex.
+
+**Passos:**
+1. Read `CONTEXT.md` no diretório atual (arquivo pequeno — OK ler completo)
+2. `wc -l "$VAULT/projetos/$PROJ.md"` → tail Read das últimas 60 linhas
+3. Identificar diferenças em: estado atual, pendências, decisões
+4. Edit cirúrgico em `projetos/[nome].md` (só seções alteradas)
+5. `grep -n "Última sessão\|Pendente" "$VAULT/CEREBRO.md" | grep -i "$PROJ"` → Edit linha
+6. Append linha em `_index/sessions.md`
+7. Confirmar em 2 linhas

package/src/skills-lib/cerebro/references/comandos-rotina-e-captura.md

@@ -0,0 +1,94 @@
+# Comandos de Rotina e Captura: /dia, /dump, /decisao, /conteudo
+
+Carregue este arquivo ao executar `/dia`, `/dump`, `/decisao` ou `/conteudo`. Antes de tudo, releia a REGRA DE OURO e a seção Vault no SKILL.md principal — esses comandos dependem delas.
+
+## /dia
+
+**Objetivo:** briefing de início do dia. Ler apenas o essencial de cada projeto ativo.
+
+**Passos:**
+1. `grep -A4 "### " "$VAULT/CEREBRO.md"` → lista todos os blocos de projeto (nome + última sessão + pendente)
+2. Para cada projeto com status ativo (🟢🟡): tail-read de 30 linhas (`offset=n-30`)
+3. Montar briefing consolidado
+4. Não ler `_knowledge/goals.md` a menos que o usuário peça explicitamente
+
+**Formato de saída:**
+```
+## Briefing — [data]
+
+**[Projeto]** — [emoji status]
+↳ Última sessão: [data] — [resumo]
+↳ Pendente: [items]
+
+**Foco sugerido:** [1-2 linhas]
+```
+
+## /dump
+
+**Objetivo:** captura rápida. Zero reads.
+
+**Passos:**
+1. Receber o conteúdo (do argumento ou perguntar em 1 mensagem)
+2. Classificar: ideia / aprendizado / decisão / referência / conteúdo
+3. Write direto no arquivo certo — sem ler nada antes
+4. `grep -n "## Conteúdo em aberto\|## Aprendizados" "$VAULT/CEREBRO.md"` → achar linha para Edit de 1 linha
+5. Confirmar em 1 linha
+
+## /decisao
+
+**Objetivo:** registrar decisão. Zero reads de arquivos existentes.
+
+**Passos:**
+1. Receber descrição + alternativas + projeto (perguntar tudo de uma vez se não passado)
+2. Write direto em `_decisions/YYYY-MM-DD-[slug].md` (template abaixo)
+3. `grep -n "## Decisões recentes" "$VAULT/CEREBRO.md"` → linha
+4. Edit para inserir referência wiki-link logo abaixo dessa linha
+5. Se há projeto: `grep -n "## Decisões" "$VAULT/projetos/$PROJ.md"` → Edit 1 linha
+
+**Template `_decisions/YYYY-MM-DD-[slug].md`:**
+```markdown
+# [Título]
+> Data: [data] | Projeto: [[projetos/nome]] | Status: ativa
+
+## Decisão
+[1-2 linhas]
+
+## Contexto
+[por que foi necessária]
+
+## Alternativas
+- [A] — descartada: [motivo]
+- [B] — descartada: [motivo]
+
+## Raciocínio
+[por que esta]
+
+## Consequências
+[o que muda]
+```
+
+## /conteudo
+
+**Objetivo:** capturar ideia de conteúdo. Zero reads.
+
+**Passos:**
+1. Receber ideia + plataforma + formato + gancho + CTA (perguntar tudo de uma vez)
+2. Write direto em `_content/YYYY-MM-DD-[slug].md`
+3. `grep -n "## Conteúdo em aberto" "$VAULT/CEREBRO.md"` → Edit 1 linha abaixo
+
+**Template `_content/YYYY-MM-DD-[slug].md`:**
+```markdown
+# [Título]
+> Data: [data] | Plataforma: [plataforma] | Status: ideia
+
+## Ideia
+[1-3 linhas]
+
+## Formato / Gancho / CTA
+- Formato: [tipo]
+- Gancho: [o que torna diferente]
+- CTA: [ação / objetivo]
+
+## Rascunho
+[espaço livre]
+```

package/src/skills-lib/cerebro/references/comandos-sessao.md

@@ -0,0 +1,122 @@
+# Comandos de Sessão: /iniciar, /ver, /salvar
+
+Carregue este arquivo ao executar `/iniciar`, `/ver` ou `/salvar`. Antes de tudo, releia a REGRA DE OURO e a seção Vault no SKILL.md principal — esses comandos dependem delas.
+
+## /iniciar
+
+**Objetivo:** configurar projeto novo. Só cria arquivos — não lê nada além do CEREBRO.md mínimo.
+
+**Passos:**
+1. Descobrir vault (ver seção Vault)
+2. `grep -c "$PROJ" "$VAULT/CEREBRO.md"` → verificar se projeto já existe (0 = novo)
+3. Se novo: entrevistar em 1 mensagem (organização, info essencial, estilo, modo)
+4. Write `projetos/[nome].md` com template
+5. `grep -n "## Projetos" "$VAULT/CEREBRO.md"` → Edit para inserir entrada
+6. Confirmar
+
+**Template `projetos/[nome].md`:**
+```markdown
+# [Nome] — Estado Atual
+> Atualizado: [data]
+
+## Preferências
+- Organização: [resposta]
+- Info essencial: [resposta]
+- Estilo: [resposta]
+- Modo: [registro / sugestivo]
+
+## Stack
+[breve descrição]
+
+## Onde parou
+-
+
+## O que falta
+- [ ]
+
+## Sessões
+| Data | Resumo |
+|------|--------|
+|      |        |
+```
+
+**Template bloco em CEREBRO.md:**
+```markdown
+### [Nome] [emoji]
+- **Stack:** [stack]
+- **Última sessão:** [data] — [resumo]
+- **Pendente:** [pendências]
+- **Estado atual:** [[projetos/nome]]
+```
+
+## /ver
+
+**Objetivo:** mostrar estado atual rápido. Máximo: 1 Read.
+
+**Passos:**
+1. `wc -l "$VAULT/projetos/$PROJ.md"` → total de linhas
+2. Read com `offset=(n-60)`, `limit=60` → pega Onde parou + O que falta + Sessões
+3. Retornar em formato condensado:
+
+```
+## [Projeto] — [data última sessão]
+Stack: [1 linha]
+Onde parou: [bullets]
+O que falta: [checkboxes]
+Última sessão: [1 linha]
+```
+
+## /salvar
+
+**Objetivo:** fechar sessão, persistir o que aconteceu. Máximo de tokens: ~800 input + edits.
+
+**Passos (executar em ordem, sem desvios):**
+
+**1. Localizar projeto e bloco no CEREBRO.md (1 bash call)**
+```bash
+VAULT=~/Documents/projects/Obsidian\ Vault
+PROJ=construcao   # inferir do diretório atual ou contexto
+grep -n "### \|Última sessão\|Pendente" "$VAULT/CEREBRO.md" | grep -A2 -i "$PROJ"
+wc -l "$VAULT/projetos/$PROJ.md"
+```
+
+**2. Ler apenas o final do arquivo do projeto (1 Read)**
+- `offset = (total_linhas - 80)`, `limit = 80`
+- Isso captura: Hoje atual, Onde parou, O que falta, tabela Sessões
+
+**3. Construir as alterações na memória, depois aplicar (Edits atômicos)**
+
+Em `projetos/[nome].md`, sempre adicionar ACIMA da seção "Onde parou" existente:
+```markdown
+## Hoje ([data] — [sessão])
+- [item 1]
+- [item 2]
+```
+
+Substituir "Onde parou" e "O que falta" com o estado novo.
+
+Adicionar linha na tabela Sessões (append na última linha da tabela).
+
+**4. Atualizar bloco do projeto em CEREBRO.md (1 Edit)**
+- Usar grep do passo 1 para saber as linhas exatas
+- Edit cirúrgico apenas nas linhas "Última sessão" e "Pendente"
+
+**5. Atualizar CONTEXT.md (Edit cirúrgico — só campos alterados)**
+- Nunca reescrever o arquivo inteiro
+- Editar apenas: data no cabeçalho, pendências em "O que falta", commit hash se mudou
+
+**6. Append em `_index/sessions.md` (1 Edit ou Write se não existir)**
+```markdown
+| [data] | [projeto] | [resumo 1 linha] |
+```
+
+**7. Se houve decisão ou aprendizado relevante:** criar arquivo em `_decisions/` ou `_learnings/` (Write direto, sem Read prévio).
+
+**8. Higiene do índice (compactação)**
+```bash
+wc -l "$VAULT/CEREBRO.md"
+```
+- Se > 150 linhas: mover o conteúdo mais antigo/menos essencial (projeto ✅ concluído ou ❌ descontinuado com histórico longo, ou entradas de "Decisões recentes" além das ~15 mais novas) para `_index/cerebro-archive.md`, deixando no lugar só 1 linha de referência `[[_index/cerebro-archive]]`. Nunca apagar, só mover.
+- Se ≤ 150 linhas: pular este passo.
+
+**9. Confirmar em 2 linhas** o que foi salvo.

package/src/skills-lib/content-strategy/SKILL.md

@@ -16,327 +16,25 @@ If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-
 
 Gather this context (ask if not provided):
 
-### 1. Business Context
-- What does the company do?
-- Who is the ideal customer?
-- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
-- What problems does your product solve?
-
-### 2. Customer Research
-- What questions do customers ask before buying?
-- What objections come up in sales calls?
-- What topics appear repeatedly in support tickets?
-- What language do customers use to describe their problems?
-
-### 3. Current State
-- Do you have existing content? What's working?
-- What resources do you have? (writers, budget, time)
-- What content formats can you produce? (written, video, audio)
-
-### 4. Competitive Landscape
-- Who are your main competitors?
-- What content gaps exist in your market?
-
----
+1. **Business Context** — What does the company do? Who is the ideal customer? What's the primary goal for content (traffic, leads, brand awareness, thought leadership)? What problems does your product solve?
+2. **Customer Research** — What questions do customers ask before buying? What objections come up in sales calls? What topics appear repeatedly in support tickets? What language do customers use to describe their problems?
+3. **Current State** — Do you have existing content? What's working? What resources do you have (writers, budget, time)? What formats can you produce (written, video, audio)?
+4. **Competitive Landscape** — Who are your main competitors? What content gaps exist in your market?
 
 ## Searchable vs Shareable
 
-Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.
-
-**Searchable content** captures existing demand. Optimized for people actively looking for answers.
-
-**Shareable content** creates demand. Spreads ideas and gets people talking.
-
-### When Writing Searchable Content
-
-- Target a specific keyword or question
-- Match search intent exactly—answer what the searcher wants
-- Use clear titles that match search queries
-- Structure with headings that mirror search patterns
-- Place keywords in title, headings, first paragraph, URL
-- Provide comprehensive coverage (don't leave questions unanswered)
-- Include data, examples, and links to authoritative sources
-- Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web
-
-### When Writing Shareable Content
-
-- Lead with a novel insight, original data, or counterintuitive take
-- Challenge conventional wisdom with well-reasoned arguments
-- Tell stories that make people feel something
-- Create content people want to share to look smart or help others
-- Connect to current trends or emerging problems
-- Share vulnerable, honest experiences others can learn from
-
----
-
-## Content Types
-
-### Searchable Content Types
-
-**Use-Case Content**
-Formula: [persona] + [use-case]. Targets long-tail keywords.
-- "Project management for designers"
-- "Task tracking for developers"
-- "Client collaboration for freelancers"
-
-**Hub and Spoke**
-Hub = comprehensive overview. Spokes = related subtopics.
-```
-/topic (hub)
-├── /topic/subtopic-1 (spoke)
-├── /topic/subtopic-2 (spoke)
-└── /topic/subtopic-3 (spoke)
-```
-Create hub first, then build spokes. Interlink strategically.
-
-**Note:** Most content works fine under `/blog`. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's `/agile` guide). For typical blog posts, `/blog/post-title` is sufficient.
-
-**Template Libraries**
-High-intent keywords + product adoption.
-- Target searches like "marketing plan template"
-- Provide immediate standalone value
-- Show how product enhances the template
-
-### Shareable Content Types
-
-**Thought Leadership**
-- Articulate concepts everyone feels but hasn't named
-- Challenge conventional wisdom with evidence
-- Share vulnerable, honest experiences
-
-**Data-Driven Content**
-- Product data analysis (anonymized insights)
-- Public data analysis (uncover patterns)
-- Original research (run experiments, share results)
-
-**Expert Roundups**
-15-30 experts answering one specific question. Built-in distribution.
-
-**Case Studies**
-Structure: Challenge → Solution → Results → Key learnings
-
-**Meta Content**
-Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."
-
-For programmatic content at scale, see **programmatic-seo** skill.
-
----
-
-## Content Pillars and Topic Clusters
-
-Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content.
-
-Most of the time, all content can live under `/blog` with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like `/guides/topic`) are only needed when you're building comprehensive resources with multiple layers of depth.
-
-### How to Identify Pillars
-
-1. **Product-led**: What problems does your product solve?
-2. **Audience-led**: What does your ICP need to learn?
-3. **Search-led**: What topics have volume in your space?
-4. **Competitor-led**: What are competitors ranking for?
-
-### Pillar Structure
-
-```
-Pillar Topic (Hub)
-├── Subtopic Cluster 1
-│   ├── Article A
-│   ├── Article B
-│   └── Article C
-├── Subtopic Cluster 2
-│   ├── Article D
-│   ├── Article E
-│   └── Article F
-└── Subtopic Cluster 3
-    ├── Article G
-    ├── Article H
-    └── Article I
-```
-
-### Pillar Criteria
-
-Good pillars should:
-- Align with your product/service
-- Match what your audience cares about
-- Have search volume and/or social interest
-- Be broad enough for many subtopics
-
----
-
-## Keyword Research by Buyer Stage
-
-Map topics to the buyer's journey using proven keyword modifiers:
-
-### Awareness Stage
-Modifiers: "what is," "how to," "guide to," "introduction to"
-
-Example: If customers ask about project management basics:
-- "What is Agile Project Management"
-- "Guide to Sprint Planning"
-- "How to Run a Standup Meeting"
-
-### Consideration Stage
-Modifiers: "best," "top," "vs," "alternatives," "comparison"
-
-Example: If customers evaluate multiple tools:
-- "Best Project Management Tools for Remote Teams"
-- "Asana vs Trello vs Monday"
-- "Basecamp Alternatives"
+Every piece of content must be searchable, shareable, or both. Prioritize in that order — search traffic is the foundation.
 
-### Decision Stage
-Modifiers: "pricing," "reviews," "demo," "trial," "buy"
+**Searchable content** captures existing demand: target a specific keyword/question, match search intent exactly, use titles/headings that mirror search patterns, place keywords in title/headings/first paragraph/URL, provide comprehensive coverage, and optimize for AI/LLM discovery (clear positioning, structured content, brand consistency across the web).
 
-Example: If pricing comes up in sales calls:
-- "Project Management Tool Pricing Comparison"
-- "How to Choose the Right Plan"
-- "[Product] Reviews"
+**Shareable content** creates demand: lead with a novel insight or counterintuitive take, challenge conventional wisdom with well-reasoned arguments, tell stories that make people feel something, and share vulnerable, honest experiences.
 
-### Implementation Stage
-Modifiers: "templates," "examples," "tutorial," "how to use," "setup"
+## References (load on demand)
 
-Example: If support tickets show implementation struggles:
-- "Project Template Library"
-- "Step-by-Step Setup Tutorial"
-- "How to Use [Feature]"
-
----
-
-## Content Ideation Sources
-
-### 1. Keyword Data
-
-If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:
-- Topic clusters (group related keywords)
-- Buyer stage (awareness/consideration/decision/implementation)
-- Search intent (informational, commercial, transactional)
-- Quick wins (low competition + decent volume + high relevance)
-- Content gaps (keywords competitors rank for that you don't)
-
-Output as prioritized table:
-| Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |
-
-### 2. Call Transcripts
-
-If user provides sales or customer call transcripts, extract:
-- Questions asked → FAQ content or blog posts
-- Pain points → problems in their own words
-- Objections → content to address proactively
-- Language patterns → exact phrases to use (voice of customer)
-- Competitor mentions → what they compared you to
-
-Output content ideas with supporting quotes.
-
-### 3. Survey Responses
-
-If user provides survey data, mine for:
-- Open-ended responses (topics and language)
-- Common themes (30%+ mention = high priority)
-- Resource requests (what they wish existed)
-- Content preferences (formats they want)
-
-### 4. Forum Research
-
-Use web search to find content ideas:
-
-**Reddit:** `site:reddit.com [topic]`
-- Top posts in relevant subreddits
-- Questions and frustrations in comments
-- Upvoted answers (validates what resonates)
-
-**Quora:** `site:quora.com [topic]`
-- Most-followed questions
-- Highly upvoted answers
-
-**Other:** Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord
-
-Extract: FAQs, misconceptions, debates, problems being solved, terminology used.
-
-### 5. Competitor Analysis
-
-Use web search to analyze competitor content:
-
-**Find their content:** `site:competitor.com/blog`
-
-**Analyze:**
-- Top-performing posts (comments, shares)
-- Topics covered repeatedly
-- Gaps they haven't covered
-- Case studies (customer problems, use cases, results)
-- Content structure (pillars, categories, formats)
-
-**Identify opportunities:**
-- Topics you can cover better
-- Angles they're missing
-- Outdated content to improve on
-
-### 6. Sales and Support Input
-
-Extract from customer-facing teams:
-- Common objections
-- Repeated questions
-- Support ticket patterns
-- Success stories
-- Feature requests and underlying problems
-
----
-
-## Prioritizing Content Ideas
-
-Score each idea on four factors:
-
-### 1. Customer Impact (40%)
-- How frequently did this topic come up in research?
-- What percentage of customers face this challenge?
-- How emotionally charged was this pain point?
-- What's the potential LTV of customers with this need?
-
-### 2. Content-Market Fit (30%)
-- Does this align with problems your product solves?
-- Can you offer unique insights from customer research?
-- Do you have customer stories to support this?
-- Will this naturally lead to product interest?
-
-### 3. Search Potential (20%)
-- What's the monthly search volume?
-- How competitive is this topic?
-- Are there related long-tail opportunities?
-- Is search interest growing or declining?
-
-### 4. Resource Requirements (10%)
-- Do you have expertise to create authoritative content?
-- What additional research is needed?
-- What assets (graphics, data, examples) will you need?
-
-### Scoring Template
-
-| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total |
-|------|----------------------|-------------------------|----------------------|-----------------|-------|
-| Topic A | 8 | 9 | 7 | 6 | 8.0 |
-| Topic B | 6 | 7 | 9 | 8 | 7.1 |
-
----
-
-## Output Format
-
-When creating a content strategy, provide:
-
-### 1. Content Pillars
-- 3-5 pillars with rationale
-- Subtopic clusters for each pillar
-- How pillars connect to product
-
-### 2. Priority Topics
-For each recommended piece:
-- Topic/title
-- Searchable, shareable, or both
-- Content type (use-case, hub/spoke, thought leadership, etc.)
-- Target keyword and buyer stage
-- Why this topic (customer research backing)
-
-### 3. Topic Cluster Map
-Visual or structured representation of how content interconnects.
-
----
+- `references/content-types.md` — searchable formats (use-case content, hub and spoke, template libraries) and shareable formats (thought leadership, data-driven content, expert roundups, case studies, meta content). Load when picking the concrete format for a topic.
+- `references/pillars-and-keywords.md` — how to identify and structure the 3-5 content pillars/topic clusters, plus keyword modifiers and examples mapped to each buyer-journey stage (awareness, consideration, decision, implementation). Load when building the pillar architecture or mapping a topic to a buyer stage.
+- `references/ideation-sources.md` — how to mine keyword exports, call transcripts, survey responses, forums (Reddit/Quora), competitor blogs, and sales/support input for content ideas. Load when the user hands you raw research inputs, or when you need to go find ideas yourself.
+- `references/prioritization-and-output.md` — the 4-factor scoring model (customer impact, content-market fit, search potential, resource requirements) with a scoring template, and the output format for the final content strategy (pillars, priority topics, cluster map). Load when ranking a backlog of ideas or formatting the deliverable.
 
 ## Task-Specific Questions
 
@@ -346,8 +44,6 @@ Visual or structured representation of how content interconnects.
 4. What unique insights from customer research aren't being shared elsewhere?
 5. Which existing content drives the most conversions, and why?
 
----
-
 ## Related Skills
 
 - **copywriting**: For writing individual content pieces

package/src/skills-lib/content-strategy/references/content-types.md

@@ -0,0 +1,52 @@
+# Content Types
+
+Load this file when picking a concrete content format for a searchable or shareable topic.
+
+## Searchable Content Types
+
+**Use-Case Content**
+Formula: [persona] + [use-case]. Targets long-tail keywords.
+- "Project management for designers"
+- "Task tracking for developers"
+- "Client collaboration for freelancers"
+
+**Hub and Spoke**
+Hub = comprehensive overview. Spokes = related subtopics.
+```
+/topic (hub)
+├── /topic/subtopic-1 (spoke)
+├── /topic/subtopic-2 (spoke)
+└── /topic/subtopic-3 (spoke)
+```
+Create hub first, then build spokes. Interlink strategically.
+
+**Note:** Most content works fine under `/blog`. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's `/agile` guide). For typical blog posts, `/blog/post-title` is sufficient.
+
+**Template Libraries**
+High-intent keywords + product adoption.
+- Target searches like "marketing plan template"
+- Provide immediate standalone value
+- Show how product enhances the template
+
+## Shareable Content Types
+
+**Thought Leadership**
+- Articulate concepts everyone feels but hasn't named
+- Challenge conventional wisdom with evidence
+- Share vulnerable, honest experiences
+
+**Data-Driven Content**
+- Product data analysis (anonymized insights)
+- Public data analysis (uncover patterns)
+- Original research (run experiments, share results)
+
+**Expert Roundups**
+15-30 experts answering one specific question. Built-in distribution.
+
+**Case Studies**
+Structure: Challenge → Solution → Results → Key learnings
+
+**Meta Content**
+Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."
+
+For programmatic content at scale, see **programmatic-seo** skill.