agentsclimarketplace
Sign in

Investigate

Skill allemaar/open-skills/skills/investigate

Gather facts (files, deps, patterns) without making changes. Trigger when the user runs /investigate or asks to "look into this", "explore the codebase", "understand how this works", "what files are involved", "map the dependencies", or wants read-only fact-gathering before deciding what to do.From its SKILL.md

Install
npx -y skills add allemaar/open-skills --skill investigate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, 600 tokens by cl100k_base, as published. Nobody here has run it

/investigate

Read-only fact-gathering — understand the codebase before acting.

Structured execution spec: protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the @STAMP date.

Caller Options. Before executing, run the Caller Options protocol (caller-options/SKILL.md): triage this invocation for material optionality across the venues and modes declared in front-matter; if one path clearly dominates, proceed silently; otherwise surface the options to the caller. A resolved-invocation marker means COP already ran — execute the fixed combination directly, do not re-enter COP.

Fact-Gathering Protocol. READ ONLY. No plans, no code, no refactors. Just facts.

Phase 1 — Context Loading

  1. Parse the query — identify target files, directories, or concepts from the user's request.
  2. List files — read the target directory structure.
  3. Read entrypoints — load package.json, README.md, index files, or whatever serves as the front door to the target area.

Phase 2 — Pattern Discovery

  1. Search for usages — grep for functions, components, or patterns relevant to the query. Follow call sites and import chains.
  2. Load relevant skills — check if a domain skill applies:
    • If your repository maintains its own standards skills (UI conventions, coding standards), load the matching one — this pack does not ship them.
    • Otherwise → any matching installed skill for additional context

Phase 3 — Reporting

Output a structured fact report:

  • Files Found — paths to all relevant files, not just descriptions
  • Patterns Used — architectural or implementation patterns in play
  • Dependencies — what this area depends on; what depends on it
  • Constraints Discovered — existing conventions, locked APIs, shared types — anything that would constrain a future implementation

Rules

  • MUST NOT create plans or write code — read only
  • MUST include file paths in the report, not just descriptions

Human output. This skill's handler-facing output obeys the human-output contract (human-output/SKILL.md).

Next skills. On completion, run the Next Skills protocol (next-skills/SKILL.md): surface the next-skills recommendations from front-matter for the caller to pick. Offer only — never auto-invoke.

Self-improvement. On completion, run the Self-Improvement Protocol (self-improve/SKILL.md): if this run surfaced a concrete, blocking-or-recurring weakness in this skill, propose a specific fix for the handler to approve. Conservative — silent otherwise. Never auto-apply.

What ships with it: 1 file

4.9 KB alongside SKILL.md

Gives 0 of the 12 instructions most research analysis skills give in 600 tokens

Counted across 1,213 of the 2,113 authors here whose files we hold, read 2026-09-06

  • Cite sources for every important claimin 47 of 1213, across 38 files
  • Separate facts from inferences and recommendationsin 21 of 1213, across 12 files
  • Write findings to a markdown filein 19 of 1213
  • Label every insight with a confidence levelin 18 of 1213, across 8 files
  • Read product marketing context before asking questionsin 18 of 1213, across 8 files
  • Rank themes by frequency and intensityin 16 of 1213, across 6 files
  • Establish research mode before proceedingin 16 of 1213, across 6 files
  • Segment survey responses by customer tier or tenurein 16 of 1213, across 6 files
  • Categorize support tickets before analyzingin 16 of 1213, across 6 files
  • Weight research sources from the last twelve monthsin 16 of 1213, across 6 files
  • Use at least five data points per segmentin 15 of 1213, across 5 files
  • Extract verbatim quotes for all research findingsin 15 of 1213, across 5 files

Said here and by no other author read

  • Run caller options protocol before executing
  • Parse the user query for targets
  • Read entrypoint files
  • Follow call sites and import chains
  • Output a structured fact report
  • Include file paths in the report

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.