Research & Search

fdiblen Bundle

Covers community peer review of research software: preparing a package for JOSS, pyOpenSci or rOpenSci submission, self-checking against their review criteria before submitting, writing the paper or statement of need, responding to reviews, and acting as a reviewer or CODECHECK-style codechecker who executes the artifact. Use when the user mentions JOSS, pyOpenSci, rOpenSci or CODECHECK, wants to submit software for peer review or publication, asks whether their package is review-ready, or is reviewing someone else's research software for one of these venues. (PR-level code review is rseng-version-control-review; overall publication channel strategy is rseng-software-publishing.)

fdiblen Bundle

Covers data management plans (DMPs) for research projects: what funders require, drafting a DMP from the project's actual data reality (types, volumes, storage, sharing, preservation, responsibilities, costs), machine-actionable DMPs (RDA common standard, Data Stewardship Wizard, DMPonline funder templates), and keeping the plan synchronized with practice. Use when a proposal or project needs a DMP, when the user mentions data management plans, maDMPs, DS-Wizard or DMPonline, when funder or institutional data policy applies, or when the existing DMP has drifted from what the project actually does with its data. (Day-to-day data practice is rseng-data-management; the software management plan twin is rseng-management-planning.)

fdiblen Bundle

Covers making research code faster with evidence: profiling before optimizing (py-spy and language-native profilers), interpreting hotspots, choosing optimizations by measured payoff, benchmark regression tracking with airspeed velocity (asv), and scaling measurements. Use when the user says their code is slow, asks to optimize or speed something up, wants benchmarks or performance regression tests, or before recommending rewrites, parallelism or GPUs on performance grounds.

fdiblen Bundle

Covers the researcher-facing open science workflow: setting up OSF projects that link materials, data, code and registrations, preregistering studies and analysis plans, depositing preprints and linking them to published versions, participating in open peer review, and choosing openness levels honestly. Use when the user mentions open science, OSF, preregistration, registered reports or preprints, wants their research process (not just the software) open, asks where to preregister or preprint, or when a project's openness claims should become verifiable practice.

fdiblen Bundle

Covers using version control effectively for research software and the PR-time review process: choosing a VCS, branching and commit practice, authorship and signatures in commit metadata (author/committer identity, Co-authored-by trailers, signed commits and tags, .mailmap), collaboration on GitHub/GitLab, and constructive checklist-driven pull-request reviews. Use when the user asks how to set up git, design a branching strategy, write commit messages, record who authored or co-authored a change, sign commits or tags, handle large binary files, open or review a pull/merge request, or wire linters and CI into review. (Audits of existing code and milestone reviews: rseng-code-review; pre-reviewing your own draft: rseng-pair-programming.)

fdiblen Bundle

Covers making research software environments reproducible: pinning a language version and its dependencies in a per-project virtual environment, choosing a package/environment manager, and packaging code and its full stack into a container. Use when the user asks how to set up venv/conda/poetry/uv/renv, lock or pin dependencies, share a runnable environment, escape "dependency hell" or "works on my machine", write a Dockerfile, build an Apptainer/Singularity image for HPC, or decide between a virtual environment and a container. For regenerating a project's results end to end see rseng-reproducibility; for environments of multi-step pipelines see rseng-workflows.

fdiblen Bundle

Covers keeping research software alive and responsible over time: ongoing maintenance practice, tracking and paying down technical debt, reducing the bus factor, and deprecating or archiving honestly. Use when the user asks how to maintain or sustain a project, stop it rotting, schedule CI to catch breakage from external change, track or pay down tech debt, plan maintenance funding or shared ownership, or retire or deprecate software. (Energy and carbon footprint of computing is rseng-green-computing; dependency updating and auditing detail is rseng-dependency-management; archiving mechanics are rseng-archiving.)

ticruz38 Bundle

Summarize articles and documents with key point extraction

ticruz38 Bundle

Find relevant and trending hashtags for social media content

dtsong Skill

Use when answering a federal, state, or international tax question that requires authoritative research. Covers IRC, Treasury Regs, Rev Rul/Proc, case law, and applicable treaty positions. Do not use for tax-provision computation (use finance-provision — Phase 3+).

dtsong Skill

Use when the council needs to surface organizational knowledge buried across multiple internal sources (wikis, design docs, ADRs, past tickets, postmortems, chat archives, code repos). Plans where to look, what to cross-reference, and how to synthesize findings into evidence the council can act on. Do not use for external market research (use competitive-analysis), library evaluation (use library-evaluation), or technology trend assessment (use technology-radar).

kirodotdev Skill

What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.

drn Skill

Scheduled KB maintenance — ingest yesterday's meetings + session captures, synthesize raw notes into existing topical docs (decisions, people changes, conventions), resolve conflicts, age out stale entries, fix frontmatter and links. Translates raw data into knowledge. Runs unattended; never asks for confirmation. Use for KB maintenance, knowledge base cleanup, dream consolidation, memory hygiene, or as a scheduled daily KB pass.

drn Skill

Run a structured retrospective or post-incident review with optional knowledge base capture. Use for running retrospectives, postmortems, or incident reviews.

drn Skill

Time-boxed technical investigation with structured findings document, tech spike, research spike, proof of concept. Use for time-boxed research, technical spikes, or proof of concept work.

drn Skill

Initialize or update a project knowledge base for durable cross-session knowledge capture. Use for setting up or updating project knowledge bases.

irahardianto Skill

Document architectural decisions using ADR format. Use during research when choosing approaches, introducing deps/patterns, or changing arch.

r-irbe Skill

USE FOR: orchestrating a 5-member Lean 4 research council (Α / Β / Γ / Δ / Ε) — RESEARCH loop (dual to RALPH), Rumsfeld epistemic mapping (known/unknown × known/unknown), cross-disciplinary research domains (Mathlib / AI / Physics / Bio / Social), session protocol, literature synthesis, self-improvement meta-loop. DO NOT USE FOR: single proof or single literature lookup (use @lean-research); proof review (use @lean-review-council); synthesis-only emission (use @research-synthesis-engine); proof itself (use @lean-proof). TRIGGERS: research council, RESEARCH loop, Rumsfeld matrix, epistemic mapping, research session, literature synthesis council, cross-disciplinary research.

r-irbe Skill

USE FOR: mapping a domain's concept lattice, identifying load-bearing assumptions, surfacing implicit ontologies, drafting an epistemic terrain map. DO NOT USE FOR: producing formal proofs (use @lean-proof), gathering primary research data (use @applied-intelligence-analysis). TRIGGERS: concept-map, ontology, terrain, epistemic-survey.

r-irbe Skill

USE FOR: creating fleeting/literature/permanent ZK notes during Lean proof reviews, linking notes bidirectionally, running synthesis after a council session, detecting orphan and island notes, maintaining `_index.md` and `_tags.md`. DO NOT USE FOR: running the review council itself (use @lean-review-council), reviewing a single proof (use @lean-proof-review), updating external papers from results (use @lean-doc-improvement), authoring the review methodology retro (use @lean-retro-methodology), generating a project blueprint (use @lean-blueprint). TRIGGERS: zettel, ZK-, fleeting note, permanent note, synthesis.

r-irbe Skill

REDIRECT — the typed research protocols (M/T/L/S/D/X/E) previously hosted here have been folded into `lean-research` Part 9. This stub preserves the slug for Ctrl-F discoverability and incoming cross-references (per the zero-deletions Chesterton protocol).

r-irbe Skill

USE FOR: Strategic mathematical thinking — brainstorming, problem decomposition, proof strategy design, creative hypothesis generation, and mathematical intuition development. Use when facing novel formalization challenges, when standard approaches fail, when exploring connections between domains, or when the theorem specification needs creative mathematical insight. The creative counterpart to the systematic research-council and review-council skills. DO NOT USE FOR: strategy analysis methodology generally (use @applied-strategy-analysis); research synthesis (use @research-synthesis-engine); Lean specification (use @lean-specification). TRIGGERS: strategy studio, brainstorming, problem decomposition, proof strategy, creative hypothesis, mathematical intuition.

r-irbe Skill

USE FOR: Lean 4 package and toolchain research — evaluating Reservoir/GitHub packages, Mathlib/cslib pin changes, Lake dependency health, package adoption classes, update sequencing, and external theorem-substrate candidates. Use this whenever the user asks whether to add, update, fork, pin, vendor, or reject a Lean package, even if they phrase it as "can we use this repo?" or "does mathlib have this now?". DO NOT USE FOR: ordinary theorem lookup without a package decision (use @lean-research); package-file mutation or `lake update` execution (use @lean-enforcement plus a project-specific edit claim); proof writing (use @lean-proof); general project QA (use @lean-quality-engine). TRIGGERS: Lean package, Reservoir, GitHub Lean repo, Lake dependency, lake-manifest, lean-toolchain, mathlib update, cslib update, package adoption, package pin, dependency health, external theorem substrate.

r-irbe Skill

USE FOR: running a Lean 4 corpus retrospective — RETRO protocol (Refactor-Extract-Test-Refine-Optimize), adapting to project scale (Solo / Small / Medium / Large), per-phase enforcement scripts, cross-skill optimization rules, retro personas, tracking documents, embedded RALPH inside RETRO phases. DO NOT USE FOR: single proof review (use @lean-proof-review); council convocation (use @lean-review-council); research (use @lean-research); enforcement gate execution alone (use @lean-enforcement). TRIGGERS: retro, retrospective, RETRO protocol, refactor extract test refine optimize, retro phase, retro session, corpus retro, cross-skill optimization.

r-irbe Skill

USE FOR: running the 5-role synthesis engine (Α-S Scanner / Β-S Clusterer / Γ-S Distiller / Δ-S Verifier / Ε-S Publisher) — Scan-Cluster-Distill-Verify-Publish (SYNTHESIZE) loop, four product tiers (Quick / Standard / Deep / Comprehensive), duality with the review-council RALPH loop, domain cross-references, Mathlib coverage tracking. DO NOT USE FOR: single-source literature review (use @lean-research); proof or formalization work (use @lean-proof or @lean-ai-formalization); review of a finished synthesis (use @lean-review-council); Zettelkasten card emission only (use @lean-zettelkasten). TRIGGERS: synthesis, SYNTHESIZE loop, synthesis council, Α-S, Β-S, Γ-S, Δ-S, Ε-S, scanner, clusterer, distiller, verifier, publisher, quick synthesis, deep synthesis.

oimiragieo Skill

Use when writing or auditing any blog post on your product's site (new post or existing). Enforces the BlogPostLayout container contract AND a Tier-1/Tier-2 anti-AI-slop checklist derived from 15-source Exa research (2026-05-14). Both checks are mandatory before any blog post merges.

oimiragieo Skill

Use when deciding whether to BUILD or DEFER a researched feature pre-revenue — the demand-signal-over-stated-interest, set-threshold-first, prereq-chain, written-defer-brief discipline (the build-now-vs-defer axis, distinct from an act-vs-ask common-sense-gate axis).

oimiragieo Skill

Use BEFORE writing any code that extracts an archive, downloads a binary/wheel/tarball, installs a dependency or tool, self-upgrades a running binary, or bootstraps a toolchain (rustup/uv/mise). Triggers on: 'extract a zip/tar', 'extractall', 'download the release asset', 'self-update/auto-upgrade helper', 'install script', 'pin the dependency', 'cargo/npm/pip install in CI', 'bootstrap the toolchain'. Encodes 6 production-shipped, citation-backed hardening checks: zip-slip guard before extractall; time-bound + byte-capped downloads; checksum-gated FAIL-CLOSED installs (incl. detached self-upgrade helpers, verify before os.replace); --locked + exact version pins for CI tools; fail-closed-with-explicit-opt-in for unverified toolchains; committed-checksum for platform installers whose native bootstrap skips binary verification (uv .ps1/.sh). Apply BEFORE writing the code, not after.

oimiragieo Skill

Use when a task is too big for a handful of subagents or needs cross-verification — codebase audits, multi-file migrations, cross-checked research, plan-from-N-angles, multi-source sweeps. Codifies the built-in Workflow tool (dynamic workflows), the authoring API, quality patterns, the framework-decision rule, what to download, and this project's reusable templates + house constraints.

wulaosiji Bundle

长文生成与深度写作工具，支持结构化长文（2000字以上）的生成，包括教程、研究报告、分析报告等。 Use when: "写一篇深度教程", "生成研究报告", "扩写大纲", "长文写作", "详细分析报告", "多章节文档", "generate long tutorials", "write research reports", "expand outline", "in-depth analysis". Cross-references: md-to-wechat, image-ocr, infographic-generator. Built by UniqueClub 🌐 https://uniqueclub.ai

stevennitesh Bundle

Research questions or compare options requiring source evaluation, synthesis, or reconciliation of conflicting evidence. Exclude quick factual lookups and runnable experiments.

stevennitesh Bundle

Research and value a publicly traded company from current primary evidence. Use for fair value, intrinsic value, DCF or reverse DCF, residual income, forward P/E or PEG, comparable-company valuation, earnings or guidance tied to valuation, margin of safety, or a fundamental thesis. Route unsupported methods to explicit capability gaps. Do not use for technical analysis, short-term price forecasts, trade execution, portfolio sizing, or personalized investment advice.

stevennitesh Bundle

Coordinate an explicitly requested parallel implementation across bounded items, with exclusive ownership, safe integration, cross-item proof, and recoverable worktree cleanup. Use for implementation fanout, not parallel research or a single coding task.

stevennitesh Skill

Use when approved repo work should be coordinated through a plan document, GitHub issues, one verified implementation or research issue at a time, and an explicit checkpoint policy.

synaptiai Skill

Record every material claim as a row in `00-control/evidence-ledger.md` carrying a source-authority level and a claim state (verified, corroborated, reported, inferred, unknown, not applicable), and keep observed, interpreted, unknown, and recommended content in visibly separate blocks. Use when inventorying sources, when drafting any sentence that asserts a fact, or when a verification pass asks what backs a claim. This skill MUST be consulted because an assertion without an `[EV-####]` citation and a claim state is indistinguishable from a guess, and a package whose claims cannot be traced to executable reality fails diligence at the first spot-check.

leoyishou Bundle

深度调研工具，支持多信息源并发搜索、多任务类型策略。可指定信息源（reddit/twitter/perplexity/v2ex）或任务类型（痛点挖掘/舆情分析/投资情绪/技术调研）。