Explore skills
Showing 17401–17430 of 21985 skills
Builds or audits a literature review: evidence map, closest prior work, gap verdict, and synthesis plan. Use to check whether a contribution is novel, map what a literature establishes, or organize a review; systematic reviews get a protocol scaffold.
scdenney/open-science-skills
Stars: 70Claude CodeCodexRun one consequential, contestable decision through a deliberative committee of GPT-6 Astra and Claude Opus, chaired by fable (default), astra, opus, or sol. Not for factual lookups, brainstorming, routine implementation, independent-coder reliability, or final professional judgment. Use when several options are defensible and the two model families should propose, critique, revise, and cross-rank under a predeclared rubric.
scdenney/open-science-skills
Stars: 70Claude CodeCodexOrchestrate complex work from an active gpt-6-astra or gpt-6.1-sol Codex session. The detected lead owns decomposition, integration, and verification; Astra keeps the hardest reasoning in the lead, while Sol escalates unusually difficult units to Astra. Both route bounded work to Sol at medium effort, mechanical work to Luna, and can use a cross-vendor Claude peer. Not for routine single-context work. Use when the user explicitly asks to orchestrate, delegate, fan out, parallelize, assign subagents, obtain independent checks, or have Codex act as tech lead.
scdenney/open-science-skills
Stars: 70Claude CodeCodexRun a pre-submission manuscript audit covering argument, numerics, references, writing, figures, methods, preregistration, and replication readiness. Add --codex for a cross-model pass in which Codex and Claude review independently and verify each other's findings.
scdenney/open-science-skills
Stars: 70Claude CodeCodexTypeset a working paper or journal submission in house-style LaTeX from Markdown, Word, TeX, ODT, RTF, or HTML. Use to convert drafts, build PDFs, or prepare journal-specific spacing, limits, anonymization, disclosures, and citations.
scdenney/open-science-skills
Stars: 70Claude CodeCodexScaffold or audit a social-science replication package, and audit the manuscript and archived research objects against FAIR. Use when setting up or repairing a package, checking one before submission, or drafting data, code, and materials availability statements. Adapted from Yusaku Horiuchi's replication-package-guide.
scdenney/open-science-skills
Stars: 70Claude CodeCodexInterviews a researcher in rounds (idea, design, or defend stage) until no decision in a research idea, design, or draft is left assumed, recommending an answer to each question and writing settled decisions to a file. Use for 'grill me', stress-testing a design, or an idea not yet a design; --plan for software or process plans.
scdenney/open-science-skills
Stars: 70Claude CodeCodexScaffold or audit a research-project repository organized around its source library (PDFs, Markdown conversions, bibliography, intake pipeline) plus the analysis, manuscript, and review folders it needs. Use when starting or auditing a research repo. Not for one-PDF intake or publication replication packages.
scdenney/open-science-skills
Stars: 70Claude CodeCodexPlans a research project as a durable decision map, resolving one design decision per session until the design is defensible and pre-registerable. Use at project start, when a design has more open decisions than one conversation holds, or when planning keeps restarting. Not for running analyses or writing the paper.
scdenney/open-science-skills
Stars: 70Claude CodeCodexStart-of-session report on where a repository stands. Reads the project's own handoff and log files, checks live git state, and reports objective, verified baseline, open tasks, blockers, and next actions. Use when resuming work. Twin of finished.
scdenney/open-science-skills
Stars: 70Claude CodeCodexDesign and format publication-quality tables. Use for column order, row grouping, notes, statistical precision, accessibility, and reproducibility.
scdenney/open-science-skills
Stars: 70Claude CodeCodexAdvises on setting up and validating topic models for survey and experimental text: discovery vs. measurement, STM/LDA/BERTopic choice, preprocessing, covariate formulas, choosing K across coherence, FREX, held-out likelihood, and residuals, validating topics against human coding, robustness, and reporting. Coding against a fixed codebook goes to text-classification.
scdenney/open-science-skills
Stars: 70Claude CodeCodexAppend-only log of settled project decisions and learnings, shown at session start. Use when asked to "log this decision", "record that we decided", "supersede decision", "what did we decide", "/learn", "remember this lesson", or "show learnings".
tonone-ai/tonone
Stars: 82Claude CodeCodexOpt-in session guard that confirms destructive commands and freezes edits to one directory. Use when asked to "be careful", "freeze edits to src/", or "guard this session".
tonone-ai/tonone
Stars: 82Claude CodeCodexPlan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
tonone-ai/tonone
Stars: 82Claude CodeCodexEngineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
tonone-ai/tonone
Stars: 82Claude CodeCodexWeekly engineering retrospective from git history. Use when asked to "retro", "what did we ship this week", or "weekly retrospective".
tonone-ai/tonone
Stars: 82Claude CodeCodexCross-cutting multi-lens review of a diff — parallel security/backend/data/test lenses, red-team pass, merged verdict. Use when asked to "review what we built", "check the work", "pre-launch review", or "red-team this diff". Not the skill-manifest gate.
tonone-ai/tonone
Stars: 82Claude CodeCodexOptional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
tonone-ai/tonone
Stars: 82Claude CodeCodexTurn a flow that just worked in this session into a reusable skill. Use when asked to "skillify this", "make this a skill", or "save this workflow".
tonone-ai/tonone
Stars: 82Claude CodeCodexCTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
tonone-ai/tonone
Stars: 82Claude CodeCodexWrite an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
tonone-ai/tonone
Stars: 82Claude CodeCodexMaintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
tonone-ai/tonone
Stars: 82Claude CodeCodexMap the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
tonone-ai/tonone
Stars: 82Claude CodeCodexGenerate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".
tonone-ai/tonone
Stars: 82Claude CodeCodexGenerate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
tonone-ai/tonone
Stars: 82Claude CodeCodexDocumentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".
tonone-ai/tonone
Stars: 82Claude CodeCodexRender agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
tonone-ai/tonone
Stars: 82Claude CodeCodexEvaluate model performance — check for accuracy drops, data drift, and error patterns. Use when asked about "model accuracy dropped", "evaluate the model", "check for drift", or "model performance".
tonone-ai/tonone
Stars: 82Claude CodeCodexDesign and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
tonone-ai/tonone
Stars: 82Claude CodeCodex