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 stefanoskarakasis/Product-Marketing-Skills --skill meta-learngit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-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/stefanoskarakasis/product-marketing-skills/meta-learn)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/meta-learn"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/meta-learn/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/stefanoskarakasis/product-marketing-skills/meta-learn"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/meta-learn.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.00132 | $0.01882 |
| Opus 5 | $0.00066 | $0.00941 |
| Sonnet 5 | $0.00026 | $0.00376 |
| Haiku 4.5 | $0.00013 | $0.00188 |
Grade A, and why
meta-learn 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 today.
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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meta-learn
The deliberate, on-demand deep-dive into a completed skill session — for
when the automatic one-line Learning Close every T1/T2 skill already writes
isn't enough. Asks what the session actually taught the user — not what the
skill's output said, but what surprised them, what they disagreed with, or
what was missing. Turns real answers into a specific, falsifiable statement
and logs it to the same file, in the same format, every T1/T2 skill's own
Learning Close writes to — so meta-synthesis reads one consistent log
regardless of which produced any given row.
Trigger
-
When: The user wants a deeper capture of a completed skill session than the automatic one-line row every T1/T2 skill already logs at its own close (see that skill's Learning Close step). Use this for a session that deserves real reflection — something surprised the user, a recommendation felt wrong, or important context was missing — and a structured three-question interview is worth the extra few minutes.
-
Not for: Auditing a
SKILL.md's structure → usemeta-review. Checking whether a skill's output itself is correct → usemeta-verify. Detecting patterns across multiple sessions or proposing guardrails → usemeta-synthesis, which reads what this skill logs. -
Example prompts:
- "Capture what we learned from that retro"
- "Log this session"
- "What surprised you about that positioning run?"
- "Save the learnings before we close"
Inputs
- Args: The completed session's skill name and a short description of
its output.
n.v.t.if invoked immediately after a skill session in the same conversation — infer both from context. - Defaults: If the skill name isn't obvious, ask for it before proceeding.
- Context keys:
/context/skill-sessions.md— appended to, created if it doesn't exist yet.
Pre-flight
- This skill is context-agnostic. Do not load
/foundation/brain.mdand do not let prior company context shape what counts as a pattern — extraction comes from the user's answers alone. - If there's no completed session to close out (skill hasn't produced output yet), stop and say so — this isn't a mid-session check-in.
What ships with it
1 file 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.
- today Changed · +2 lines 5df66b63a799
- 12d ago First seen · 196 lines · 132 tokens per session scan A ba710171b050
meta-learn is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (5 stars, last pushed today), licensed MIT. It adds 132 tokens to every session and 1,882 once invoked, about $0.0007 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
becoming-senior-pm
Use this skill when the user asks "how do I become a senior PM", "what does senior PM actually mean", "I want to get promoted to senior", "what's the difference between PM and senior PM", "I've been a PM for 2–3 years and want to grow", "my manager says I need to work more strategically", "I'm stuck at PM level", or…
memory
Use this skill when the user asks to "update my PM Copilot memory", "save this to my profile", "remember that", "update my context", "update my product context", "save this decision", "add this to my memory", "track this risk", "mark this risk as resolved", "add a lesson learned", "save these stakeholder notes", or…
solo-to-cpo
Use this skill when the user asks about "career path to CPO", "how do I become a CPO", "PM career progression", "path from PM to VP Product", "PM career growth", "how do I grow as a PM", "what does the PM career ladder look like", "solo PM to product leader", or wants to understand and plan their PM career trajectory…
technical-pm
Use this skill when the user asks about "working with engineers as a PM", "how technical should a PM be", "I feel out of my depth with engineers", "how to earn engineering trust", "how to read code as a PM", "should I learn to code", "bridging the gap with engineering", "technical credibility for PMs", or wants to…
vibe-coding
Use this skill when the user asks to "vibe code this", "build this with AI", "help me use Cursor/v0/Bolt to build this", "vibe coding from my PRD", "how do I code this with AI", "turn this spec into code", or wants guidance on using AI coding tools (Cursor, GitHub Copilot, v0, Bolt, Lovable, Claude Artifacts) to…
eval-suite-design
Use this skill when the user asks to "design an eval suite", "build evals for my AI feature", "create an evaluation framework", "how do I evaluate my AI", "what evals should I run", "build an eval system", or wants to create a systematic evaluation framework for an AI-powered product feature. Typically run after…