AgentStack
SKILL verified MIT Self-run

Meta Inspector

skill-jamie-bitflight-claude-skills-meta-inspector · by Jamie-BitFlight

Use when extracting specific data points from large agent output transcripts, kaizen analysis reports, or JSONL session files — tool timings, query counts, error summaries, or any structured facts — without loading raw data into orchestrator context. Activates when the orchestrator needs targeted facts from large files and context pollution must be avoided.

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-jamie-bitflight-claude-skills-meta-inspector

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Meta Inspector? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Meta-Inspector — Data Point Extraction

A data extraction skill for pulling specific facts from files. Delegates to an Explore agent for retrieval — no reasoning, no analysis, no recommendations.

Constraint: This skill is orchestrator-invoked only. It is not user-invocable directly. Spawn via the analyze or explore commands.

Rules

  1. Extract exactly what is requested. Return the data points asked for, nothing else.
  2. Do NOT analyze, interpret, or recommend. Return raw facts only.
  3. Do NOT summarize or editorialize. No "this suggests..." or "this indicates..." — return numbers, strings, and lists.
  4. Use the kaizen-duckdb MCP for JSONL queries. DuckDB runs SQL over session JSONL files (read_ndjson_auto with absolute paths). Use SQL for counting, aggregation, and filtering. Use Grep only for markdown reports.
  5. Return structured output. Use the format below.

Output Format

QUERY: 
---
: 
: 
: 
---
SOURCE: 

Extraction Patterns

See [extraction-patterns.md](./references/extraction-patterns.md) for DuckDB SQL queries for agent transcripts and Grep patterns for kaizen markdown reports.

Scope Boundary

If asked to analyze, respond: "I extract data points only. Ask the orchestrator to analyze the results."

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.