Depure e inspecione especificações KGF — visualize resultados de tokenização, árvores de análise e arestas extraídas de arquivos fonte. Use ao adicionar/corrigir suporte a linguagens ou quando a saída de análise do indexion parecer incorreta.
Esta skill, chamada `trkbt10/indexion-kgf`, foi projetada para desenvolvedores que trabalham com o analisador indexion e precisam depurar especificações KGF (Knowledge Graph Format). Ela permite inspecionar visualmente os resultados da tokenização de arquivos fonte, exibindo árvores de análise sintática e arestas extraídas, o que é crucial ao adicionar suporte a novas linguagens ou corrigir problemas no comportamento do indexion. Suportada por ferramentas como Claude Code, Cursor ou Codex, a skill simplifica o processo de validação e ajuste fino de gramáticas KGF, ajudando a identificar erros de análise ou tokenização que possam gerar saídas incorretas. Ao usar comandos e scripts de depuração, o desenvolvedor pode iterar rapidamente sobre suas especificações, garantindo que o indexion produza resultados precisos e consistentes.
npx skills add https://github.com/trkbt10/indexion-skills/tree/main/skills/indexion-kgfInstalled? Explore more Pesquisa e Análise de Dados skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
Depure e inspecione especificações KGF — visualize resultados de tokenização, árvores de análise e arestas extraídas de arquivos fonte. Use ao adicionar/corrigir suporte a linguagens ou quando a saída de análise do indexion parecer incorreta.
This repo contains 8 individual skills — each has its own dedicated page.
Generate and use a pre-edit structure brief so coding agents learn likely owners, consumer surfaces, and unsafe edit locations before implementing.
Documentation analysis — assess coverage, detect code-to-doc drift with plan reconcile, visualize dependencies with doc graph. Answers "what needs docs?" and "are docs still accurate?"
Detect and review name/content drift in code using `indexion identity audit`, then plan verified renames, moves, folder changes, or splits.
README construction — initialize template structure, generate per-package READMEs from doc comments, plan writing tasks, assemble root README from docs/ and package READMEs via doc.json config, and verify edits with `plan drift`.
After writing code, detect and clean up duplication at three levels — copy-paste blocks, cross-package shared code, unnecessary wrappers, and concept-level SoT violations. Detect with indexion, fix, and verify.
Generate SDD requirements from RFCs/specs and quantitatively verify implementation conformance. spec draft → spec align → spec verify → automated validation loop with codex/claude. Operate spec-to-impl drift gates as CI checks.
Split text into contextual chunks for RAG/embedding pipelines. Document segmentation and section extraction using window, tfidf, punctuation, or hybrid strategies chosen by intent.
Project wiki lifecycle — create pages, track source changes with ingest, update stale pages, lint structural integrity, detect code-to-doc drift with reconcile, and manage search indexes. A runbook for navigating and maintaining the wiki as an agent.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.