research_progress

Evaluates research ideas through value, related-work, and feasibility checks before experiment design.

5|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/WissingChen/my_code_config --skill research-progress-wissingchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research_progress
Source: https://github.com/WissingChen/my_code_config/tree/main/my_skills/research_progress
Command: npx skills add https://github.com/WissingChen/my_code_config --skill research-progress-wissingchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Research ideas often jump straight to experiment design without verifying whether the problem is worth solving, whether prior work already solved it, or whether the implementation chain is even feasible. This Skill grounds research directions in reality first, so experiments only run when they resolve a decision-relevant uncertainty. ## Core Features & Use Cases - Four-Stage Convergence Gate: Sequentially checks value (who is blocked, metric-to-goal chain), related-work reality (implementation-level facts via knowledge_keeper), end-to-end implementation feasibility (labeled arrow chain), and which single uncertainty to verify first. - Speculation Tracking: Maintains a speculation ledger scoring each unverified claim by guesswork level, failure impact, and verification cost to prioritize the cheapest decisive test. - Decision-Driven Experiments: Rejects experiments that do not target the top-ranked uncertainty, requiring pre-written actions for each possible outcome before anything runs. - Use Case: A researcher proposes applying causal intervention to radiology report generation. The Skill challenges the framing, delegates literature checks, maps the implementation chain, and outputs a verdict (rejected / blocked / evaluating / passed) with the single next decision-changing evidence item. ## Quick Start Ask the assistant to evaluate whether your proposed research direction is worth pursuing and what should be verified first.

Frequently Asked Questions about research_progress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a research idea is worth pursuing?▼

Run the idea through four sequential checks: who is concretely blocked by the problem, what prior work actually achieved at implementation level, whether the end-to-end chain from data to evaluation closes, and which single uncertainty most blocks the next decision. Ideas failing any gate are rejected or marked blocked.

How to decide which experiment to run first in a research project?▼

Score each unverified assumption on guesswork level, failure impact, and verification cost, then multiply the scores. Run only the cheapest test targeting the highest-priority uncertainty, with pre-written actions for each possible outcome before starting.

When should a research direction be stopped or rejected?▼

Reject when no specific user is blocked, when the only novelty is combining two existing things, when success requires unrealistic inputs or compute, or when strong prior work already solved the problem. Mark blocked when data, interfaces, or code availability remain unverified.

Does this skill design or run experiments itself?▼

No. It only converges ideas to a pass/reject verdict and identifies the single next decision-changing verification. Experiment execution, branching, and artifact management are handed off to the experiment_manager skill after a proposal passes.

What are the limitations of speculation-based research planning?▼

Reasoning and simulation can only prioritize which assumptions to test; they cannot serve as evidence. Predicting experiment outcomes without running them is explicitly forbidden, since recorded cases show such predictions being contradicted by actual measurements.