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 guia-matthieu/clawfu-skills --skill one-on-onesgit clone --depth 1 https://github.com/guia-matthieu/clawfu-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/guia-matthieu/clawfu-skills/one-on-ones)<a href="https://agentmods.dev/skills/guia-matthieu/clawfu-skills/one-on-ones"><img src="https://agentmods.dev/badge/skills/guia-matthieu/clawfu-skills/one-on-ones/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/guia-matthieu/clawfu-skills/one-on-ones"><img src="https://agentmods.dev/badge/skills/guia-matthieu/clawfu-skills/one-on-ones.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.00099 | $0.01671 |
| Opus 5 | $0.00049 | $0.00835 |
| Sonnet 5 | $0.00020 | $0.00334 |
| Haiku 4.5 | $0.00010 | $0.00167 |
Grade A, and why
one-on-ones 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 9d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One-on-Ones
Design and run effective 1:1 meetings that build trust, develop people, and surface problems before they become crises.
When to Use This Skill
- New manager setting up 1:1s for the first time
- Resetting unproductive 1:1s that became status updates
- Onboarding a new direct report with structured first conversations
- Preparing for a difficult conversation (performance, conflict, change)
- Career development coaching in 1:1 context
- Scaling management as team grows
Methodology Foundation
| Aspect | Details |
|---|---|
| Sources | Andy Grove (High Output Management), Kim Scott (Radical Candor), Michael Lopp (Managing Humans) |
| Core Principle | The 1:1 is the direct report's meeting, not the manager's — their time to surface what matters to them |
| Key Ratio | Manager talks 10-30% of the time; listens 70-90% |
What Claude Does vs What You Decide
| Claude Does | You Decide |
|---|---|
| Designs 1:1 cadence and structure for your team size | Personal relationship-building approach |
| Generates conversation frameworks and question banks | Which questions fit each person |
| Creates agenda templates and running-notes docs | How to adapt for individual personalities |
| Prepares scripts for difficult conversations | Final wording and tone for sensitive topics |
| Suggests development discussion frameworks | Career advice based on your knowledge of the person |
Instructions
Step 1: Set Up the Mechanics
Cadence by maturity:
| Task-Relevant Maturity | Frequency | Duration |
|---|---|---|
| New or struggling | 2x/week | 30-45 min |
| Developing | Weekly | 30-45 min |
| Senior / independent | Bi-weekly | 45-60 min |
Rules: Same time each week. Rarely cancel. They own the agenda (shared doc, they add topics first). Private space for sensitive topics.
30-minute structure:
| Time | Activity |
|---|---|
| 0-5 min | Check-in: "How are you, really?" |
| 5-20 min | Their agenda items |
| 20-25 min | Your topics (feedback, context) |
| 25-30 min | Commitments and close |
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.
- 9d ago First seen · 160 lines · 99 tokens per session scan A 3dff9dca8092
one-on-ones is a skill published in the GitHub repository guia-matthieu/clawfu-skills (149 stars, last pushed 5mo ago), licensed MIT. It adds 99 tokens to every session and 1,671 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-09-03.
Other skills, from other repositories
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
developer-onboarding-builder
Création de processus d'onboarding pour nouveaux développeurs. Se déclenche avec "onboarding", "nouveau développeur", "intégration équipe", "setup poste", "getting started guide", "accueil développeur". Also triggers on "onboard a new developer", "developer setup guide", "first week checklist".
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
ads-performance-analytics
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media…
paid-media-strategy
A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media…
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.