finder-reactor
Skill2 starsChanged 41 days agoMITView on GitHub
Core autonomous, self-guarded decision loop for opportunity-finder apps. Handles discovery (e.g. X search), analysis (LLM + CV + platform context), prep generation, tracking, and guarded promote with cost/rate/fit/CV mutation guards, human pause points, structured decisions, and logging. Use when designing, implementing, or debugging the agentic heart of a finder platform. Fission for tight loops; fusion for reactor architecture and surplus.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-auditSkill
- agentic-reactorSkill
- agent-orchestratorSkill
- ai-optimizationSkill
- architecture-synthesisSkill
- audit-allow-buildsSkill
- audit-ide-dependenciesSkill
- author-workflow-skillSkill
- bdd-strategizerSkill
- chrome-extension-mv3Skill
- concurrent-cli-agentsSkill
- control-feederSkill
- control-graphSkill
- cursor-transcript-harvestSkill
- cv-promote-guardSkill
- devcontainer-hardenedSkill
- dual-copy-skill-publishSkill
- explore-repo-readonlySkill
- fix-dependency-securitySkill
- fusion-sageSkill
- git-worktreesSkill
- grok-host-prepSkill
- gt-flowSkill
- higher-order-decision-architectSkill
- looperSkill
- master-plannerSkill
- mvu-refactor-planSkill
- odysseus-navigatorSkill
- project-editor-profileSkill
- react-client-expertSkill
- semantic-markup-cssSkill
- semantic-nameSkill
- session-unit-orderSkill
- shell-kernel-ontologySkill
- skill-rename-propagationSkill
- split-to-prsSkill
- src-tree-reorganizeSkill
- stellar-roadmapSkill
- stellar-spacemapSkill
- subagent-delegationSkill
- subagent-explore-reportSkill
- supply-chain-hardenSkill
- tauri-agenticSkill
- tauri-ipc-debugSkill
- tidy-commit-pushSkill
- upgrade-packagesSkill
- verification-cockpitSkill
- x-agent-resourcesSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Every arrow has a guard or pause hook.
- Distinctive: line 45
Before expensive LLM batch.
- Very specific: line 55
Fusion: Treat as FinderReactor state machine.
- Distinctive: line 61
Never send full raw CV JSON or unpruned threads to LLM unless user explicitly asks for "deep mode" with confirmation.
- Distinctive: line 62
Never write to external profile CV without sidecar + preview + two explicit confirms.
- Distinctive: line 63
Always surface rate limit headers and estimated spend.
- Distinctive: line 64
All autonomous "decide" outputs must include confidence (0–100) and intervention level.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Finder Reactor — Self-Guarded Opportunity Engine
Load rule: Formal SoT. Fission loops → ai-optimization; architecture/surplus → fusion-sage; CV writes → cv-promote-guard.
CLT: ../rules/clt-dual-load.mdc — HITL pauses stay short+decisive; agent loop may continue in parallel until a human gate fires.
// Mission
Finder ≔ search → analyze → decide → prep → track → (promote?) → surplus
// with guards + HITL pauses on high stakes
// Axioms
A1 Guard ≻ Speed // named check + audit before threshold cross
A2 Pause on stakes/ambiguity // CV promote, low conf, cost/rate, writes
A3 Human owns query // never hide "best" search
A4 Sidecar-first external mutation // promote proposal before master write
A5 Decide outputs structured // conf + guards + rationale (zod/serde)
A6 Surplus after every cycle
A7 Reversible + auditable // JSON state; .bak + git-friendly CV diffsReactor Loop (Conceptual State Machine)
Search (tunable query + platform context)
→ Ingest + Classify
→ Analyze (pruned CV packet + platform skill/llms + post → fit, gaps, angle, confidence)
Guard: cost, rate, basic validity
→ Decide (structured: pursue? score? prep now? pause for user? why?)
→ Prep (if cleared): letter, cv-delta, research, outreach (guarded)
→ Present + Track (UI/MCP)
→ Export / Apply (user or approved agent action)
→ Outcome → Learn
→ Promote (if pattern or explicit): guarded path to external CV repo
→ SurplusEvery arrow has a guard or pause hook.
Pause / Intervention Points (UI toasts/dialogs + MCP ask_user tool):
- Before expensive LLM batch.
- On fit 60–85 or "interesting but stretch".
- Before any promote.
- On rate limit approaching or cost budget hit.
- On low confidence decision.
Implementation Patterns
Fission: Prune CV to "CorePacket"; prune platform posts; token budget on every prompt; structured output schemas.
Fusion: Treat as FinderReactor state machine; cross-cutting guards (CVPromoteGuard, CostGuard, RateGuard, DecisionLogger, SurplusGenerator); persist "what worked".
MCP / Skill Exposure: Key entry points as MCP tools (search, analyze, prep, decide, promote). Document in root SKILL.md (agentskills.io style).
Guardrails (Non-Negotiable)
- Never send full raw CV JSON or unpruned threads to LLM unless user explicitly asks for "deep mode" with confirmation.
- Never write to external profile CV without sidecar + preview + two explicit confirms.
- Always surface rate limit headers and estimated spend.
- All autonomous "decide" outputs must include confidence (0–100) and intervention level.
- Reactor dev: follow bdd-strategizer for guard + pause logic.
Activation for Agents
- Architecture / new guard design: load finder-reactor + fusion-sage.
- Specific guard, prompt, or MCP tool: ai-optimization + cv-promote-guard, x-agent-resources, tauri-agentic.
- Parallel Rust vs React vs prompts: agent-orchestrator + git-worktrees.
Surplus Generation (Mandatory After Reactor Changes)
⚡ Finder Surplus (Q ≈ X.X)
This change would have [saved Y tokens / avoided Z bad decisions] on recent opportunities.
Concrete future win: [specific example].
Suggested follow-up: [one compounding improvement].Track in .agents/skills/finder-reactor/surplus-log.md or fusion-state.
Related
x-agent-resources, cv-promote-guard, tauri-agentic, ai-optimization, fusion-sage, agentic-reactor.
Example provenance: battle-tested on collab-finder.
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
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.

