CommunityInvestigación y análisis de datosgithub.com

Meta-Inspector — Extracción de Puntos de Datos

Se utiliza para extraer puntos de datos específicos de grandes transcripciones de salida de agentes, informes de análisis kaizen o archivos de sesión JSONL — tiempos de herramientas, recuentos de consultas, resúmenes de errores o cualquier hecho estructurado — sin cargar datos sin procesar en el contexto del orquestador. Se activa cuando el orquestador necesita hechos específicos de archivos grandes y se debe evitar la contaminación del contexto.

¿Qué es Meta-Inspector — Extracción de Puntos de Datos?

Meta-Inspector es una habilidad de extracción de datos para sistemas agentivos como Claude Code, Cursor o Codex, diseñada para extraer datos puntuales de archivos grandes (transcripciones de agentes, informes kaizen, archivos de sesión JSONL) sin cargar su contenido completo en el contexto del orquestador. Esto evita la contaminación del contexto y ahorra tokens al delegar la búsqueda a un agente Explore dedicado, que solo recupera los hechos solicitados sin realizar análisis, interpretaciones ni recomendaciones. La habilidad se activa mediante comandos `analyze` o `explore` del orquestador, y no puede ser invocada directamente por el usuario. Utiliza DuckDB MCP (con el esquema `kaizen-duckdb`) para consultas SQL sobre archivos JSONL de sesión, empleando `read_ndjson_auto` con rutas absolutas, y Grep para informes markdown de kaizen. La salida sigue un formato estructurado que incluye la consulta original, los puntos de datos extraídos con sus valores, y la fuente (ruta de archivo o consulta SQL). Si se le pide analizar, responde que solo extrae puntos de datos y sugiere al orquestador realizar el análisis.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/agentskill-kaizen/skills/meta-inspector

Installed? Explore more Investigación y análisis de datos skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →

Ver original→Ver todas las habilidades

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentación

¿Qué hace Meta-Inspector — Extracción de Puntos de Datos?

Una habilidad de extracción de datos para obtener hechos específicos de archivos. Delega en un agente Explore para la recuperación — sin razonamiento, sin análisis, sin recomendaciones.

Restricción: Esta habilidad solo se puede invocar desde el orquestador. No es invocable directamente por el usuario. Se genera mediante los comandos analyze o explore.

Reglas

  1. Extrae exactamente lo solicitado. Devuelve los puntos de datos solicitados, nada más.
  2. NO analices, interpretes ni recomiendes. Devuelve solo hechos en bruto.
  3. NO resumas ni editorialices. Nada de "esto sugiere..." o "esto indica..." — devuelve números, cadenas y listas.
  4. Usa el MCP kaizen-duckdb para consultas JSONL. DuckDB ejecuta SQL sobre archivos JSONL de sesión (read_ndjson_auto con rutas absolutas). Usa SQL para conteo, agregación y filtrado. Usa Grep solo para informes markdown.
  5. Devuelve una salida estructurada. Usa el formato a continuación.

Formato de Salida

CONSULTA: <lo que se preguntó>
---
<nombre-punto-dato>: <valor>
<nombre-punto-dato>: <valor>
<nombre-punto-dato>: <valor>
---
FUENTE: <ruta de archivo o consulta SQL utilizada>

Patrones de Extracción

Consulta patrones-de-extracción.md para consultas SQL de DuckDB para transcripciones de agentes y patrones de Grep para informes markdown de kaizen.

Límite de Alcance

Si se te pide analizar, responde: "Solo extraigo puntos de datos. Pide al orquestador que analice los resultados."

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Jamie-BitFlight/agentskill-kaizen-meta-docs

Agentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.

Jamie-BitFlight/bash-51-features

Bash 5.1 release features and improvements with practical examples. Use when working with Bash 5.1 features, epoch time variables, redirection enhancements, or when user asks about Bash 5.1 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-52-features

Bash 5.2 release features and improvements with practical examples. Use when working with Bash 5.2 features, variable handling enhancements, readline improvements, or when user asks about Bash 5.2 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-53-features

Bash 5.3 release features and improvements with practical examples. Use when working with Bash 5.3 features, new command substitution, GLOBSORT, loadable builtins, or when user asks about Bash 5.3 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-development

This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.

Jamie-BitFlight/bash-lint

This skill should be used when the user asks to "lint bash script", "run shellcheck", "format shell script", "use shfmt", "fix shellcheck errors", or mentions shell script linting, formatting, code quality, or pre-commit hooks for bash.

Jamie-BitFlight/bash-logging

This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.

Jamie-BitFlight/bash-portability

This skill should be used when the user asks about "POSIX compatibility", "portable shell scripts", "cross-shell compatibility", "bashisms", "shebang selection", or mentions writing scripts that work on different shells (bash, sh, dash, zsh) or different systems.

Jamie-BitFlight/bash-testing

This skill should be used when the user asks to "test bash script", "write shell tests", "use shunit2", "use shellspec", "create test suite for bash", or mentions unit testing, test frameworks, mocking, or test-driven development for shell scripts.

Jamie-BitFlight/brainstorming-skill

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.

Jamie-BitFlight/clang-format

Configure clang-format code formatting. Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions.

Jamie-BitFlight/commitlint

When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.

Jamie-BitFlight/conventional-commits

When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.

Jamie-BitFlight/dasel-reference

Use when querying, modifying, or converting JSON, YAML, TOML, XML, CSV, HCL, or INI with dasel v3. Complete reference for selectors, functions, conditionals, variables, spread operator, type casting, and format-specific patterns.

Jamie-BitFlight/data-exploration

Use when exploring unknown structured data files with dasel v3 — discover schema, list keys, find nested values, sample arrays, identify data types across JSON, YAML, TOML, XML, CSV, HCL, INI formats

Jamie-BitFlight/data-transformation

Use when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INI

Jamie-BitFlight/delegate

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

Jamie-BitFlight/enterprise-hibernate-hbm

Dasel v3 query patterns for Hibernate .hbm.xml mapping files — entity-table binding, Java property-to-column extraction, one-to-many set/list/bag relationship tracing, many-to-one foreign key discovery, batch scanning across 60+ HBM files. Use when querying Hibernate ORM class mappings, extracting schema metadata from Java persistence layer, or auditing entity-column relationships in enterprise legacy codebases.

Jamie-BitFlight/enterprise-installanywhere

Dasel v3 query patterns for InstallAnywhere .iap_xml installer definitions — use when querying action sequences, discovering variables, resolving platform conditions, navigating panels, or comparing installer variants. Files are 2.5+ MB, 65,000+ lines — too large for context reads, requires structural dasel queries.

Jamie-BitFlight/enterprise-maven-pom

Dasel v3 selector patterns for Maven POM XML files — use when querying dependency versions, filtering by groupId or scope, extracting module hierarchy from parent POMs, or detecting version conflicts across enterprise multi-module Java projects. Load this skill when working with pom.xml files using dasel.

Skills relacionados

affaan-m/uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.

community

affaan-m/scholar-evaluation

Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.

community

affaan-m/literature-review

Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.

community

affaan-m/everything-claude-code

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

community

forrestchang/andrej-karpathy-skills

Agent skill repository discovered by 10x-chat research.

community

langgenius/backend-code-review

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.

community
← More Investigación y análisis de datos skills