agentleFS
0-CYBERDYNE-SYSTEMS-00-CYBERDYNE-SYSTEMS-0/FFT_nano/skills/runtime/rapid-research/SKILL.md

rapid-research

Skill4 starsChanged 8 months agoMITView on GitHub

Lightweight research playbook optimized for the FF-Terminal agent.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use when another skill is a better direct match for the task.

    line 22
  2. Distinctive:

    Do not use when the request is outside this skill's scope.

    line 23
  3. Distinctive:

    Always collect at least three independent sources unless the user provided authoritative material.

    line 31
  4. Very specific:

    Keep a running source log (see templates/source_log_template.md) before drafting a summary.

    line 32
  5. Distinctive:

    Prefer deterministic helper scripts for parsing (CSV/JSON) before reasoning about them.

    line 34
  6. Very specific:

    Use ddgs (DuckDuckGo) for free, no-API-key web search.

    line 69
  7. Distinctive:

    ddgs is pre-installed in the pi container runtime: Use bash to invoke it.

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rapid Research Loop

When not to use this skill

  • Do not use when another skill is a better direct match for the task.
  • Do not use when the request is outside this skill's scope.

When to use it

  • The user needs a structured briefing, comparison table, FAQ, or short memo derived from multiple sources.
  • The task explicitly says "research", "investigate", "summarize", or requests citations/links.
  • Another agent already gathered raw notes and you must distill them.

Guardrails

  1. Always collect at least three independent sources unless the user provided authoritative material.
  2. Keep a running source log (see templates/source_log_template.md) before drafting a summary.
  3. Mark uncertainty or missing data instead of fabricating details.
  4. Prefer deterministic helper scripts for parsing (CSV/JSON) before reasoning about them.

Step-by-step workflow

  1. Clarify the question – restate the core decision or comparison criteria in one paragraph.
  2. Plan the evidence sprint – list the minimum facts you must confirm; group them by sub-question.
  3. Collect evidence – for each fact, gather a citation with date, outlet, and a one-sentence pull quote.
  4. Grade sources – label each entry with primary, secondary, or speculative.
  5. Synthesize – transform the evidence table into:
    • a 3-bullet executive summary,
    • a risk/unknowns list,
    • and next-step recommendations.
  6. Package output – use templates/research_brief_template.md as the outline and include the source log verbatim at the end.

Output template

## TL;DR (3 bullets)
- ...

## Key Findings
1. Finding + cite
2. ...

## Risks / Unknowns
- ...

## Next Best Actions
- ...

## Source Log
| Source | Date | Key Fact | Link | Confidence |
| --- | --- | --- | --- | --- |

Web Search with ddgs

Use ddgs (DuckDuckGo) for free, no-API-key web search. Available as CLI:

ddgs text -q "search query" -m 5        # text search, 5 results
ddgs news -q "search query" -m 5         # news search
ddgs images -q "search query" -m 5       # image search

Example research workflow:

# Search for evidence
ddgs text -q "OpenAI GPT-5 release date" -m 3
ddgs text -q "Claude 4 release date" -m 3

# Extract key facts from results
# (results include title, href, body/snippet)

ddgs is pre-installed in the pi container runtime. Use bash to invoke it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.