Packs

1 pack

@brycewang-stanford

Twelve-skill bundle covering the Cell manuscript lifecycle: workflow router, scope/significance fit, single-narrative framing, the Highlights + eTOC + Graphical Abstract trio, the ≤150-word Summary, main-text writing, display items, STAR Methods + Key Resources Table, data/code availability, Cell Press author–date references, submission preflight + cover letter, and reviewer rebuttal.

9 skills · pack

Results for “code-references”

3 skills

launchdarkly-automation

Manage LaunchDarkly feature flags: list projects and environments, create and delete trigger workflows, and track code references via the Composio MCP integration.

More results

ruslan-strazhnyk

Find dead code in a repo — unused exports, unreferenced files, unreachable branches, unused imports, and declared-but-unused dependencies. Reports each with file:line and a safe-to-remove confidence. Pure Claude Code, no signup.

roadrunner-build-scenario-from-osc

Build a RoadRunner Scenario programmatically from an OpenSCENARIO 1.x (.xosc) file using the `roadrunner-scenario-authoring` skill. Use when the user wants to recreate a scenario from a .xosc file, interpret an OpenSCENARIO file and build it programmatically, reconstruct a .xosc as a RoadRunner scenario, generate a MATLAB script from a .xosc file, or convert an OpenSCENARIO file to MATLAB code. Do NOT use when the user says "import" a .xosc file — that means they want RoadRunner's built-in importScenario API, not programmatic reconstruction. Handles position translation (LanePosition and RoadPosition to world coordinates), construct mapping, relative references, trajectory/route handling, parameter expressions, catalog references, and phase logic topology.