Results for “doe”
12 skills
k-dense-ai research-grants
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC with agency-specific formatting, review criteria, budget preparation, and compliance guidance.
30.2k · bundle
testdouble investigate
Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback to GitHub. Does not assess architectural health or structural risk — use architectural-analysis for architectural concerns. Does not research open-ended options, prior art, or how something works when nothing is broken — use research for that. Does not capture feedback on Han's own skills — use han-feedback for that.
218 · bundle
pantyuhov9-web repo-system-research
Research the open web for enhancement opportunities (Layer 3 — Opus subagent with WebSearch + WebFetch). Topic-driven. Returns structured findings with hype tags + source URLs. Does NOT auto-implement.
0
owl-listener empathy-map
Synthesize user research into a 4-quadrant empathy map (Says, Thinks, Does, Feels) to capture and share user understanding across a team.
1.7k
More results
brycewang-stanford research-lit
Search and analyze research papers, find related work, summarize key ideas. Use when user says "find papers", "related work", "literature review", "what does this paper say", or needs to understand academic papers.
1k
k-dense-ai experimental-design
Design experiments and studies before data collection — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable.
30.2k · bundle
alirezarezvani dossier
Produces a decision-grade dossier on a specific company, person, nonprofit, or government org by testing the user's hypothesis rather than confirming it. Outputs an editable Word document with verdict, identity facts, 12-month activity timeline, network and reputation signals, and red flags.
20.4k · bundle
testdouble han-feedback
Capture structured feedback on the Han skills and agents used in the current session and optionally post it as a GitHub issue to testdouble/han. Use at the end of any session where one or more han-* skills or agents ran, to rate a run, log what worked and what didn't, or submit observations for maintainers. Does not review code, investigate bugs, or research options; use code-review, investigate, or research for those. Does not provide feedback on skills or agents from non-Han plugins.
218
jarbitechture research
Multi-source comprehensive research using perplexity-researcher, claude-researcher, and gemini-researcher agents. Three modes - Quick (3 agents), Standard (9 agents), Extensive (24 agents with be-creative skill). USE WHEN user says 'do research', 'quick research', 'extensive research', 'find information about', 'investigate', 'analyze trends', 'current events', or any research-related request.
0 · bundle
phuryn strategy-red-team
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does, ranking failure modes by impact, likelihood, and cheapness to test.
22.6k
micsapp ask
Query the bundled research knowledge graph for methodology guidance. Routes questions through a 3-tier knowledge base — WHY (research claims), HOW (guidance docs), WHAT IT LOOKS LIKE (domain examples) — plus structured reference documents. Returns research-backed answers grounded in specific claims with practical application to the user's system. Triggers on "/ask", "/ask [question]", "why does my system...", "how should I...".
3 · bundle
testdouble pairing
Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor, for an interface contract it runs design-an-api, and for plan work it runs iterative-plan-review or plan-implementation, each collaboratively; invoke any of those directly instead to run it straight through without pausing. Does not pace someone through code that already exists and builds nothing — use code-walkthrough. Does not explain, summarize, or research something instead of producing it — use code-overview or research.
218