weorbitant/ai-dev-kit-pgi · Archived

analyze-docs

Use when searching for documentation about a concept, entity, or business term in Confluence and Notion.

First seen Jun 23, 2026

Installation

$ npx skills add weorbitant/ai-dev-kit-pgi --skill analyze-docs

Summary

  • Use when searching for documentation about a concept, entity, or business term in Confluence and Notion.
  • Extracts definitions and rules without interpretation.
  • Use when user says "busca documentación", "qué dice confluence", "analyze docs", "busca en notion", "hay documentación sobre", or "qué sabemos de".

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from weorbitant/ai-dev-kit-pgi.

npx skills add weorbitant/ai-dev-kit-pgi

Browse all from weorbitant/ai-dev-kit-pgi

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, AskUserQuestion, ToolSearch, mcp__claude_ai_Atlassian__searchConfluenceUsingCql, mcp__claude_ai_Atlassian__getConfluencePage, mcp__claude_ai_Notion__notion-search, mcp__claude_ai_Notion__notion-fetch

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,681 B
  • docs SUMMARY.md 331 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Analyze Docs

Search Confluence and Notion for documentation about a business concept. Extract definitions and rules as direct quotes — never interpret or paraphrase.

Configuration

  • Confluence Cloud ID: afianza-ac.atlassian.net

Instructions

1. Parse argument

$ARGUMENTS can be:

  • A Confluence URL → fetch that page directly
  • A Notion URL → fetch that page directly
  • Free text (concept/term) → search both platforms

If no argument, ask the user what to search for.

2. Search Confluence

ToolSearch → "select:mcp__claude_ai_Atlassian__searchConfluenceUsingCql"

Search with CQL using the terms. Try multiple queries (pass the CQL string directly as the cql parameter — no extra escaping needed):

  • Exact term: text ~ "obligación fiscal"
  • Individual words: text ~ "obligación" AND text ~ "fiscal"
  • Related terms: synonyms, abbreviations, Spanish/English variants
  • By title: title ~ "obligación"

For each relevant result, fetch the full page:

mcp__claude_ai_Atlassian__getConfluencePage(cloudId: "afianza-ac.atlassian.net", pageId: "<id>")

3. Search Notion

ToolSearch → "+notion search"
mcp__claude_ai_Notion__notion-search(query: "<terms>")

For each relevant result:

mcp__claude_ai_Notion__notion-fetch(url: "<page-url>")

4. Extract WITHOUT interpreting

For each document found, extract:

Definitions — Quote the exact text. Do not paraphrase.

"Una obligación es el compromiso fiscal o contable que..."
— Fuente: [Título página], Confluence, [link]

Business rules — Quote conditions, triggers, exceptions.

"El IVA trimestral se presenta antes del día 20 del mes siguiente..."
— Fuente: [Título página], Confluence, [link]

Diagrams/flows — Note their existence and describe what they show.

Data definitions — Any mention of fields, formats, allowed values.

5. Detect contradictions

If the same concept is defined differently in two sources, flag it:

⚠️ CONTRADICCIÓN:
   Confluence dice: "[quote A]" — [link A]
   Notion dice: "[quote B]" — [link B]

6. Output

📄 DOCUMENTACIÓN: "[término buscado]"

   CONFLUENCE:
   ┌──────────────────────────────────────────────────┐
   │ [Título página] — [link]                         │
   │ Definición: "[cita textual]"                     │
   │ Reglas: "[cita textual de reglas encontradas]"   │
   └──────────────────────────────────────────────────┘
   (repetir por cada página relevante)

   NOTION:
   ┌──────────────────────────────────────────────────┐
   │ [Título página] — [link]                         │
   │ Definición: "[cita textual]"                     │
   └──────────────────────────────────────────────────┘

   REGLAS DE NEGOCIO ENCONTRADAS:
   1. "[regla — cita directa]" — Fuente: [link]
   2. ...

   CONTRADICCIONES:
   - [fuente A] vs [fuente B]: [descripción]

   NO ENCONTRADO:
   - [términos buscados sin resultados en ninguna plataforma]

   COBERTURA:
   - Confluence: [X páginas encontradas / Y relevantes]
   - Notion: [X páginas encontradas / Y relevantes]

Edge cases

  • If Confluence MCP fails, report it and continue with Notion (and vice versa).
  • If no results in either platform, say so explicitly — "No se encontró documentación sobre [término]".
  • If a page is very long, extract only the sections relevant to the search term.
  • Never synthesize or merge definitions from multiple sources. Present each source separately.
  • If the argument contains multiple terms, search for each separately and then together.