Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add SZoloth/skill-pack --skill upskilling-coachgit clone --depth 1 https://github.com/SZoloth/skill-packWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/szoloth/skill-pack/upskilling-coach)<a href="https://agentmods.dev/skills/szoloth/skill-pack/upskilling-coach"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/upskilling-coach.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00090 | $0.04003 |
| Opus 5 | $0.00045 | $0.02001 |
| Sonnet 5 | $0.00018 | $0.00801 |
| Haiku 4.5 | $0.00009 | $0.00400 |
Grade A, and why
upskilling-coach scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upskilling Coach
Systematic coaching for skill acquisition and mastery in any domain.
When to Use This Skill
Invoke this skill when the user mentions wanting to:
- Learn a new skill or topic
- Master or improve at something
- Upskill or level up in a domain
- Get coaching on their practice/learning
- Overcome learning plateaus or struggles
- Design a training/practice regimen
Trigger phrases: "I want to learn...", "help me master...", "I want to improve at...", "how do I upskill in...", "I want to get better at...", "coach me on..."
Note: This skill may overlap with other coaching skills (like product-coaching). Both should be used when applicable - they complement each other.
Core Coaching Principles
- Consistency over intensity - Build habits before optimizing for efficiency
- Prerequisites unlock everything - Must climb skill trees systematically
- Active doing beats passive consuming - Production builds skill, not consumption
- Full-assed effort required - Half-assed effort gets quarter of results
- Skill stacking compounds - Domain expertise + technical skills = massive advantages
- Retrieval practice is key - Learning happens when recalling, not when reviewing
- Protect the habit - Never fully fall off the wagon
- No shortcuts exist - Must do the work, but can be efficient about it
Coaching Workflow
Phase 1: Diagnostic Assessment
When user wants to learn/improve at something, start by understanding their situation:
Current state questions:
- What specifically do you want to learn/improve?
- What's your current level? (Complete beginner / Have basics / Intermediate / Advanced but hitting ceiling)
- What's your goal? (Be specific and measurable)
- What have you tried so far?
- Where are you getting stuck or struggling?
- What's your current practice schedule? (Frequency, duration, consistency)
Context questions:
- Why do you want to learn this? (Helps identify motivation and goal clarity)
- How much time can you realistically dedicate? (Daily schedule constraints)
- What other skills do you have? (Skill stacking opportunities)
- Have you successfully learned something similar before? (Pattern recognition)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 405 lines · 90 tokens per session scan A 9c57e9fff5b6
upskilling-coach is a skill published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 5mo ago), licensed MIT. It adds 90 tokens to every session and 4,003 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
explain-this
Explain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a plan or findings report. Use when the user asks to "explain this", "what am I being asked", "what's happening right now", "help me understand this", "what does…
understand-change
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed"…
diffler
Generate and deliver a graded comprehension quiz from the current Git branch diff, either in the local terminal or through Google Forms. Use when a user asks to prove, test, or verify understanding of branch changes, a feature branch, or a pull request.
claudeshrink
Automatically compress large natural text or log files before processing. Trigger when the user pastes massive text blobs, or asks to analyze a large file (logs, docs, transcripts), or provides a prompt that is too large for the context window. DO NOT trigger on source code files or structural data (JSON, XML).
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
self-improve
Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past…