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 matellez/claude-skills --skill small-team-managementgit clone --depth 1 https://github.com/matellez/claude-skillsWrote 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/matellez/claude-skills/small-team-management)<a href="https://agentmods.dev/skills/matellez/claude-skills/small-team-management"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/small-team-management/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/matellez/claude-skills/small-team-management"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/small-team-management.svg" alt="Reviewed on agentmods" width="80" 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.00231 | $0.03913 |
| Opus 5 | $0.00115 | $0.01956 |
| Sonnet 5 | $0.00046 | $0.00783 |
| Haiku 4.5 | $0.00023 | $0.00391 |
Grade A, and why
small-team-management 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- small-team-management — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Small Team Management: People Skills for the Practitioner Who Came Up Through the Function
This skill addresses the people management challenges of a Director who built their career in demand gen, RevOps, or marketing operations and now manages a small team of two to six people. Most Directors in this position learned their function deeply but learned management on the job. The result is a leader who is technically excellent and managerially uneven, not because they are not capable, but because no one taught them the specific skills that make a small team work.
The problems this skill addresses are different from HR problems. HR manages processes, documentation, and legal compliance. This skill manages the actual human dynamics of a small team: how to have the feedback conversation that changes behavior, how to identify the person who is quietly underperforming before it becomes a crisis, how to run a one-on-one that is worth the time on both sides, and how to make the call on letting someone go without doing it wrong.
HOW TO SET UP THIS SKILL
Provide:
- Team size and structure: how many direct reports, what their roles are
- The specific situation: a performance issue, a feedback conversation you are preparing for, a one-on-one that is not working, or a team dynamic problem
- How long the person has been on the team and in the role
- What you have already tried
- Whether HR has been involved or needs to be
The One-on-One That Actually Works
Most one-on-ones in marketing and RevOps functions are status updates. The manager asks what is happening, the direct report gives a summary of their week, and nothing changes as a result of the conversation. That is a waste of thirty minutes for both people.
A one-on-one that functions well accomplishes three things the status update does not: it surfaces problems before they become visible to leadership, it gives the direct report a space to raise things they would not raise in a team meeting, and it builds the working relationship that makes feedback land when it needs to.
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.
- 12d ago First seen · 425 lines · 231 tokens per session scan A 015001899055
small-team-management is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 231 tokens to every session and 3,913 once invoked, about $0.0012 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-31.
Other skills, from other repositories
project-updates
Drafts Linear project status updates for each project the user leads, following the Done / In Progress / Next / Blockers template. Gathers context from Linear issues and comments, git history across configured repos, GitHub PRs, Slack mentions, Notion edits, and Gmail/Calendar. Never auto-posts — always shows the…
daily-brief
Surfaces recent updates relevant to you from GitHub, Linear, Slack, and other configured sources — PR reviews, new assignments, ticket changes, mentions, and CI failures. Use when starting work, catching up after being away, or prepping for standup.
triage-board
Generates a structured triage artifact from the current conversation's findings — a self-contained Desktop folder with a JSON Schema, schema-conformant report.json, prose markdown, and a single-file HTML viewer. Viewer ships with MD / CSV / JSON download buttons in the header and a per-finding "Copy as Markdown"…
whats-next
Suggests the 3 most impactful next actions based on full developer context — git, Linear, PRs, and current conversation. Prioritizes blockers, unblocked items, and momentum. Use when deciding what to work on next or after finishing a task.
get-up-to-speed
Reviews the latest git history, branch state, Linear ticket, and open work to build a concise situational summary. Use when picking up work after another agent, resuming a session, or onboarding to a branch mid-flight.
next-steps
Generates a stakeholder-aligned next-steps checklist for a multi-stakeholder project from the current conversation and connected context. Use when the user has just had a working session and now needs to align teammates (PM, design, engineering, leadership) on what happens next, who owns it, and what's blocked. Output…