Back to search
skill
SkillWorks with Claude CodeGitHub
claude skill
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/shreyasmehta05--skill)HTML
<a href="/listings/shreyasmehta05--skill"><img src="/api/listings/shreyasmehta05--skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 123 lines
- # Claude Code assessment kit
- ## Get it onto the machine (2 minutes)
- ```bash
- tmux
- git clone https://github.com/shreyasMehta05/skill.git ~/skill
- bash ~/skill/claude-kit/install.sh
- cd ~/candidate && claude
- ```
- Inside Claude, type `/` to see the skills, and `/hooks`, `/agents` to verify.
- Check `/model` and `/usage` (or `/cost`) once at the start.
- ## Skills available
- Type these inside Claude Code. Text after the command is optional extra focus,
- e.g. `/design keep it single-threaded` or `/optimise runtime of the feature step`.
- ### Main flow (run in this order)
- | # | Skill | What it does | Creates / updates | Then |
- | --- | --- | --- | --- | --- |
- | 1 | `/requirements` | Reads README + docs (only peeks at data) and lists deliverables, inputs, outputs, constraints, grading, open questions, traps | REQUIREMENTS.md, NOTES.md checklist | Read it, fix mistakes |
- | 2 | `/design [focus]` | Design from the requirements: components, interfaces, architecture + patterns (and one skipped), trade-offs, risks, milestones, requirement coverage. No code | DESIGN.md, DECISIONS.md | Push back, approve |
- | 3 | `/prototype [focus]` | Simplest correct end-to-end version, tests, self-check, commit, zip | code, tests, tag `m1-prototype` | |
- | 4 | `/leak-check [scope]` | One independent review (quant-reviewer on Sonnet): lookahead, leakage, bad stats, edge cases. Read-only | ranked findings list | Fix, tag `m2-validated` |
- | 5 | `/optimise [target]` | Golden output, profile, one change per `exp/` branch, before/after table. Speed or quality, whatever grading rewards | DECISIONS.md, tag `m3-optimised` | |
- | 6 | `/writeup [notes]` | Fills the report and checks every requirement is covered | SOLUTION.md | |
- | 7 | `/submit` | Builds ~/submission.zip exactly as required and verifies contents | ~/submission.zip, tag `final` | Hands off |
- ### Helpers (any time)
- | Skill | Use it when | What it does |
- | --- | --- | --- |
- | `/checkpoint [context]` | Every 15-20 min, after something works | Shows diff, runs tests, clean commit message, logs progress in NOTES.md |
- | `/decision <what + why>` | You make an important choice | Adds context / decision / alternatives / evidence to DECISIONS.md |
- | `/cpp-build [goal]` | Any C++ code | CMake debug build with sanitizers + `-O3` release build, tests, benchmarks |
- ### Reviewer agents (only run when you ask; cost nothing otherwise)
- | Agent | Ask like | Finds |
- | --- | --- | --- |
- | `quant-reviewer` | used by `/leak-check` | Lookahead, leakage, overfitting, statistical errors |
- | `perf-engineer` | "use perf-engineer to profile the pipeline" | Real hotspots + measured optimisation plan |
- | `cpp-reviewer` | "use cpp-reviewer on src/book.cpp" | UB, memory bugs, hot-path allocations, cache-unfriendly layout |
- ## Everything else in the kit
- | Piece | What it does |
- | --- | --- |
- | `CLAUDE.md` | Rules Claude follows all session: plan first, prototype then optimise, no lookahead, patterns with reasons, self-check, token saving, git and notes |
- | `templates/` | NOTES.md, DECISIONS.md, SOLUTION.md (report format), copied into ~/candidate |
- | `GIT.md` | Git guide: rhythm, commands, commit messages, tags, recovering files |
- | `guard.sh` hook | Blocks `rm -rf ~/candidate`, deleting the zip, `git reset --hard`, `git clean -f` |
- | `autocommit.sh` hook | Hidden snapshot on `refs/autosave` after every reply; your `git log` stays clean |
- | `zipit.sh` hook | Safety-net `~/submission.zip` at most every 10 min (`--force` to run now) |
- | `cpp-format.sh` hook | Auto clang-format on C++ edits (`pip install clang-format` in the venv) |
- | `statusline.sh` | Shows `[model] ctx % \| session $ \| total $/50` at the bottom of Claude Code |
- ## The 3-hour flow
- | Time (IST) | Do |
- | --- | --- |
- | 20:30 | Log in, `tmux`, clone + install, `claude` |
- | 20:35 | `/requirements`, read it, correct anything wrong. Then `/design` and **push back on it** |
- | 20:55 | `/prototype` -> working version, tests pass, zip exists |
- | 21:30 | One `/leak-check` -> fix findings (optional if self-checks were clean and budget is tight) |
- | 21:50-22:45 | `/optimise` (speed or quality, whatever the grading rewards) |
- | 22:50 | `/writeup`, then `/submit` |
- | 23:15 | Hands off. Check `unzip -l ~/submission.zip` |
- ## Prompting playbook
- **Give context, constraints and a definition of done:**
- > "Implement the order book in `book.py` per DESIGN.md section 3. Constraint:
- > O(1) cancel via id->node map, integer tick prices. Done when the 6 tests in
- > test_book.py pass and replaying data/day1 takes < 5 s. Show the timing."
- **Ask for options before committing:**
- > "Give me 3 designs for X with complexity and trade-offs. Recommend one. Don't code."
- **Make it prove things:**
- > "Before claiming it works, run it and show me the output." /
- > "Shift every feature forward by one step and re-run; if performance improves, we have a leak."
- > "Shuffle the labels; performance should drop to zero. Show me."
- **Keep it focused and cheap:**
- - One task per prompt. `/clear` between unrelated tasks; `/compact` when long.
- - Point to files (`@src/book.py`) instead of letting it search the whole tree.
- - Don't let it read large data files. Ask for `head`, shapes and dtypes only.
- - Use subagents (`/leak-check`, perf-engineer) for review: fresh eyes, separate context.
- - Press `Esc` to stop it the moment it goes the wrong way.
- **You own the design.** Graders will ask *why*. For every key choice be able to
- say what you picked, what you rejected and why. Record it in NOTES.md as you go.
- ## Saving tokens (~$50 budget)
- The status line shows `[model] ctx % | session $ | total $/50`. Total survives `/clear`.
- Change the budget with `export CLAUDE_BUDGET_USD=50` before starting `claude`.
- | Spend level | What to do |
- | --- | --- |
- | Always | One task per prompt; point at files (`@src/book.py`); `/clear` between unrelated tasks |
- | Context > 50% (yellow) | `/compact` or `/clear` (NOTES.md + DECISIONS.md carry the memory) |
- | Total > 50% before ~22:00 | Switch the main model to Sonnet with `/model` for routine coding |
- | Total > 80% (red) | Stop new features: finish, `/writeup`, `/submit` |
- - Hooks, git, zips and the status line run as shell scripts: zero tokens.
- - Claude self-checks each step (CLAUDE.md checklist), so you don't need repeated reviews.
- Run `/leak-check` once, after the prototype works (milestone m2). The reviewers are optional and cost nothing unless run.
- - Do quick things yourself: `git status`, `ls`, `head data.csv`, running a script.
- - Don't paste huge logs or data into the prompt. Paste the last 20 lines.
- - Use `/model` to check what model you're on and `/usage` (or `/cost`) for exact spend.
- ## MCP?
- Probably not needed: the task is local code + data, and Claude Code already has
- file, shell and web tools. Don't spend test time installing servers. If the
- README mentions one, add it with `claude mcp add`.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.