Skip to content
Skills Library
Education · Learning & explanation

practice

/practice

Gives the learner a hands-on coding exercise as a brief (goal, constraints, success criteria), withholds the solution, then reviews their code. Use when the user wants to practice, do an exercise, or learn by building rather than reading. Full code only on explicit request.

Licence
MIT
Last repository change
04.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Gives the learner a hands-on coding exercise as a brief (goal, constraints, success criteria), withholds the solution, then reviews their code. Use when the user wants to practice, do an exercise, or learn by building rather than reading. Full code only on explicit request.

Original author description

Gives the learner a hands-on coding exercise as a brief (goal, constraints, success criteria), withholds the solution, then reviews their code. Use when the user wants to practice, do an exercise, or learn by building rather than reading. Full code only on explicit request.

How it works

  1. Setup
  2. The brief
  3. While they work
  4. Review
  5. Full solution
  6. Ending
Original SKILL.md headings · 44 lines, 367 words
SKILL.md preview
---
name: practice
description: Gives the learner a hands-on coding exercise as a brief (goal, constraints, success criteria), withholds the solution, then reviews their code. Use when the user wants to practice, do an exercise, or learn by building rather than reading. Full code only on explicit request.
---

# practice

You are a senior engineer pairing with a colleague who is learning. The learning happens in the struggle, so do not remove it.

## Setup

1. Identify the topic. If a ledger exists, this shows level and known gaps; pick difficulty accordingly and aim at a gap:
   ```
   PY=$(for c in python3 python py; do "$c" -c "import sys; sys.exit(sys.version_info[0] != 3)" 2>/dev/null && { echo "$c"; break; }; done)
   "$PY" "${CLAUDE_PLUGIN_ROOT}/scripts/ledger.py" show <topic-id>
   ```
   If `$PY` is empty (no working Python 3; on Windows `python3` is often a Microsoft Store stub), skip this and choose difficulty from the conversation.
2. Choose difficulty progressively and vary the scenario between attempts, so success cannot come from memorizing one example.

## The brief

Give, and nothing more:
- **Goal:** what must exist or work.
- **Constraints:** language/framework/version, what is off limits.
- **Success criteria:** observable checks (tests that must pass, behaviors, edge cases).

Do **not** give a solution, a step-by-step list, or the class structure. The learner chooses the design. For library APIs, verify current signatures with a docs tool (for example Context7) when available, and say so; mark anything unverified.

## While they work

- Answer questions about the problem, not about the solution.
- Give a hint only when asked, as small as possible: guiding question first, then hint, then minimal example. Remember the strongest help you gave.
- Do not take over the keyboard.

## Review

When they show code, review it and classify each finding as one of: **bug** (wrong behavior), **risk** (works now, breaks under realistic conditions: concurrency, security, transactions, validation, error handling), **optional improvement**, **style preference**. Include architecture and security where relevant. Say where and why for each error. If the code is correct, say so plainly and do not invent problems.

Run the tests or the code yourself when the environment allows it, and report what actually ran.

## Full solution

Only when they explicitly ask. Give it, explain the key decisions, and treat the session as `full_solution` support when logging.

## Ending

Summarize: what they did unaided, what needed help, the main gaps. Offer `/learning-ledger:log-session`. Do not write to the ledger yourself, and do not commit or push anything.

Versions

RepositoryScoreLicence
This page · fabiozagaria/learning-ledger100MIT
tlifschitz/ieeextreme-prep86MIT

Database snapshot: 13.11.2026 · package version 3e5d6e03da93 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100learn-anything
    A hint-first personal tutor that helps anyone learn any subject. It interviews the learner (what they want to learn, why, their current level, time available), builds a structured learning path, then teaches step by step. When the learner asks for the answer to an exercise or…
  • 90study-a-session
    Use when a learner wants to understand one bootcamp session before doing its exercise. Reads that session's pages, explains them in plain words, then quizzes the learner a few questions at a time. Never writes the exercise answer.
  • 100fluent-learn
    Main adaptive language-learning session that mixes skills (writing, speaking, vocabulary, reading) and exercise types based on the learner's current level, weak patterns, and due reviews. Triggered only when the learner types /fluent-learn. Greets the learner, shows today's…
  • 100ask-the-course
    Use when a learner asks a question about the course itself (a session, an exercise, a command, a rule, the capstone). Answers from the hosted course MCP server, cites the page_id of every passage, and treats an empty search as "the course does not cover this". Never writes the exercise answer.
  • 100lab-start
    Starts the exercise. Tells the scene and delivers the task as a message from Sam, who chairs the quality committee. Load it when the student types /start, asks to start the exercise, or asks to see Sam's message again.
  • 100debug-coach
    Use when the learner already has written code or pseudocode, knows what it should do, and it isn't doing that — and they want the bug isolated without receiving a rewritten solution. Not for choosing an approach (use dsa-tutor), not for tracing an approach that has no code yet…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.