agentsclimarketplace

Research

Skill runxhq/runx/skills/research

the governed runtime for agent skill workflows, off the leash but on the record

Install
npx -y skills add runxhq/runx --skill research

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

What its author says it does

Copied from the file, not written here

Produce bounded, source-backed research packets for product, ecosystem, and operator decisions.

SKILL.md

4.5 KB, 885 tokens by cl100k_base, as published. Nobody here has run it

Research

Answer one practical question with enough evidence to change a decision. This skill is for applied research: which issue is worth tackling, whether a proposal is grounded, what changed in an ecosystem, or which claims a public artifact can safely make. It is not an open-ended browsing session or a summary for its own sake.

The result should make the operator's posture clearer: build, write, avoid, defer, compare, or gather a named missing fact. Prefer a small number of well-supported findings over a broad report whose conclusions cannot be traced.

Where it fits

research consumes governed source packets. Fetch or read evidence first with web-fetch, a provider-specific reader, or another skill that returns stable source and content digests. URLs, model memory, operator context, and target names do not become evidence merely because they were supplied.

The packet is a reusable primitive for deep-research, content-pipeline, ecosystem-brief, ghostwrite, product planning, and other decision workflows. It does not publish, notify, or mutate a provider. Those later operations keep their own authority, approval, and readback boundary.

How it works

  1. State a bounded objective and the decision the research should inform.
  2. Supply up to the declared source limit as governed readback packets. Runx indexes their provenance, observation times, source digests, and provider content digests before synthesis.
  3. Synthesis separates verified facts from inference, explains relevance, records confidence, and carries open questions rather than filling gaps with plausible prose.
  4. Every material claim cites an admitted source digest. Every recommended option cites the evidence on which its rationale depends.
  5. The deterministic verifier rejects unknown citations, digest drift, and unsupported decision support before the packet is released.

Return needs_more_evidence when the admitted sources cannot support the decision. Return not_worth_publishing when a finding is sound but irrelevant to the stated deliverable. Neither state is a failure; both prevent weak evidence from turning into confident downstream content.

Inputs and result

  • objective is the exact question to answer.
  • source_packets are bounded provider or fetch readback packets with stable provenance and content digests.
  • domain, deliverable, operator_context, and target_entities narrow the analysis. They are interpretation context, never source evidence.

The research packet contains the bounded brief, evidence log, decision options, risks, open questions, admitted source evidence, and deterministic validation. Consumers should carry the packet and its digest forward rather than rewriting its findings into an untraceable summary.

Stop conditions

  • Stop when no valid source packet was supplied, evidence is stale for the decision, or source identity cannot be verified.
  • Never cite an unknown source digest or treat a URL as proof that it was read.
  • Label inference as inference and lower confidence when evidence conflicts.
  • Do not manufacture balance by inventing an opposing claim with no source.
  • Keep source content out of public artifacts unless the downstream skill is allowed to use it and respects quotation and privacy constraints.
  • Route requests to browse, publish, message, or mutate to the skill that owns that boundary.

Example

An operator asks whether a proposed integration belongs in the next release and supplies a changelog readback, an issue snapshot, and an official API document. The packet can compare the evidence, state which user problem is verified, and recommend build, defer, or investigate. It cannot cite a remembered forum post or operator hunch as verified demand, and it should name the missing evidence if that gap changes the recommendation.

Agent task contract

research-synthesize

Synthesize only the supplied source index. Preserve the objective exactly and return a bounded brief, evidence log, decision support, and risks. Each material claim must cite admitted source and provider-content digests; each recommendation must cite the source digests behind its rationale. Distinguish verified evidence from inference and return needs_more_evidence when support is insufficient. Do not browse, publish, or invent provider, delivery, or certification claims.

What ships with it: 5 files

13.5 KB alongside SKILL.md

fixtures/

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

Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07

  • Generate a markdown reportin 32 of 1063, across 23 files
  • Cite each claim's sourcein 30 of 1063, across 15 files
  • Define the ideal customer profilein 20 of 1063, across 2 files
  • Search for companies matching the criteriain 20 of 1063, across 2 files
  • Assign a fit score from one to tenin 20 of 1063, across 2 files
  • Analyze the codebase to understand the productin 19 of 1063, across 1 file
  • Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
  • Look for signals of immediate needin 19 of 1063, across 1 file
  • Identify the target decision maker rolein 19 of 1063, across 1 file
  • Suggest a personalized contact strategyin 19 of 1063, across 1 file
  • Provide conversation starters for outreachin 19 of 1063, across 1 file
  • Format results in a scannable markdown templatein 19 of 1063, across 1 file

Said here and by no other author read

  • state a bounded objective and the decision it informs
  • use governed readback packets as evidence
  • synthesize admitted source packets
  • cite admitted source digests for every material claim
  • return needs_more_evidence when sources are insufficient
  • return not_worth_publishing when findings are irrelevant

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 327,132. 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.