Rapid Research Loop

AI Community

Repo stars 0
Author repo FarmFriend-Terminal-React

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Lightweight research playbook optimized for the FF-Terminal agent. Keeps | Source | Date | Key Fact | Link | Confidence | | ---…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “When to use it”, “Guardrails”, “Step-by-step workflow”, “Output template”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name Rapid Research Loop directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “When to use it / Guardrails / Step-by-step workflow” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Rapid Research Loop

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

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

Step-by-step workflow

Clarify the question – restate the core decision or comparison criteria in one paragraph.
Plan the evidence sprint – list the minimum facts you must confirm; group them by sub-question.
Collect evidence – for each fact, gather a citation with date, outlet, and a one-sentence pull quote.
Grade sources – label each entry with primary, secondary, or speculative.
Synthesize – transform the evidence table into:
- a 3-bullet executive summary,
- a risk/unknowns list,
- and next-step recommendations.
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 |
| --- | --- | --- | --- | --- |

Deterministic helpers to pair with

read_file / search_code for mining local notes or logs.
analyze_data for CSV-to-table workflows.
tavily_search or web_page_reader for live web lookups.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: AI
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @0-CYBERDYNE-SYSTEMS-0 · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview rapid-research-loop.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Rapid Research Loop

## 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 |
| --- | --- | --- | --- | --- |
```

## Deterministic helpers to pair with
- `read_file` / `search_code` for mining local notes or logs.
- `analyze_data` for CSV-to-table workflows.

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> When to use it → Guardrails → Step-by-step workflow → Output template → TL;DR (3 bullets) → Key Findings
terms    -> Clarify the question · Plan the evidence sprint · Collect evidence · Grade sources · Synthesize · Package output
files/cmd -> templates/sourcelogtemplate.md · primary · secondary · speculative · templates/researchbrieftemplate.md · readfile · searchcode · analyzedata
body sha256 -> 85de7b386007

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

Rapid Research Loop

When to use it

Guardrails

Step-by-step workflow

Output template

Deterministic helpers to pair with

Discussion