Moscow Agent Skill
MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have. Use for scope definition, feature prioritization, or when everything feels equally important.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/neurofoo/agent-skills --skill moscowWhat comes with it
8 222 bytes besides the instructionThe instruction itself
8 sections, as written by the authorMoSCoW Prioritization
Categorize items into Must have, Should have, Could have, and Won't have for clear scope and priorities.
Instructions
Take the list of items provided and sort them into MoSCoW categories. Be rigorous about what's truly a "Must"—if the project/goal can still succeed without it, it's not a Must.
Output Format
Context
What are we prioritizing for? What are the constraints (time, budget, capacity)?
Prioritized List
Must Have (Critical)
*Without these, the project fails or is pointless*
- [ ] [Item] — [Why it's a must]
- [ ] [Item] — [Why it's a must]
Should Have (Important)
*Significantly adds value; painful to omit but project survives*
- [ ] [Item] — [Value it adds]
- [ ] [Item] — [Value it adds]
Could Have (Nice to Have)
*Desirable if time permits; low impact if cut*
- [ ] [Item] — [Why it's optional]
- [ ] [Item] — [Why it's optional]
Won't Have (Not This Time)
*Explicitly out of scope; may revisit later*
- [ ] [Item] — [Why it's deferred]
- [ ] [Item] — [Why it's deferred]
Effort Distribution
| Category | Items | Est. Effort % |
|----------|-------|---------------|
| Must | X | ≤60% |
| Should | X | ~20% |
| Could | X | ~10% |
| Won't | X | 0% (deferred) |
Red Flags
- If Must > 60% of effort: scope may be too large
- If no Won'ts: probably not being honest about constraints
- If everything is Must: priorities haven't been set
Rationale
Explain the key trade-offs made and the reasoning behind contentious categorizations.
Next Step
What's the first Must item to tackle?
Guidelines
- Ask "If we shipped without this, would we fail?" for each Must
- Challenge "Musts" that are really "someone really wants this"
- Make Won'ts explicit—avoids scope creep later
- Consider dependencies (a Must might require a "hidden" Must)
- Stakeholder alignment is essential—this isn't just your opinion
$ARGUMENTS
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take neurofoo/moscow from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.