requirements-scoping
100 / 100 · Low risk
Fine to try.
This skill should be used when the user needs to "clarify requirements", separate "functional vs non-functional requirements", "scope the problem", figure out "what questions should I ask", state the "requirements for <X>", or otherwise pin down a vague design prompt before building. It turns an ambiguous ask into functional requirements, non-functional constraints, and an explicit out-of-scope. Use it whenever a prompt is broad or under-specified ("design Twitter", "build a chat app") even if …
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'requirements-scoping' ] || [ -L ~/.agents/skills/'requirements-scoping' ]; then echo 'A skill folder named requirements-scoping already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/proyecto26/system-design-skills' "$d" && git -C "$d" checkout --quiet '228d57dc6fa7627a6426553fdd6ad0040e36f361' -- 'skills/requirements-scoping' && mkdir -p ~/.agents/skills && cp -R "$d"/'skills/requirements-scoping' ~/.agents/skills/'requirements-scoping' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'requirements-scoping' ~/.claude/skills/'requirements-scoping' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/proyecto26/system-design-skills/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-07 | 228d57d | 100 |