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 dannote/dot-pi --skill chat-to-skillgit clone --depth 1 https://github.com/dannote/dot-piWrote 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/dannote/dot-pi/chat-to-skill)<a href="https://agentmods.dev/skills/dannote/dot-pi/chat-to-skill"><img src="https://agentmods.dev/badge/skills/dannote/dot-pi/chat-to-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 47 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00057 | $0.01112 |
| Opus 5 | $0.00028 | $0.00556 |
| Sonnet 5 | $0.00011 | $0.00222 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
chat-to-skill 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 8d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chat to Skill
Transform conversation history into reusable skills — long-term memory for Claude.
Process
1. Analyze Dialog
Scan the entire conversation to identify:
- Primary goal: What was the user trying to achieve?
- Secondary goals: Any related objectives discovered along the way
- Errors encountered: Mistakes, dead ends, wrong approaches
- Successful path: What actually worked
2. Abstract to Reusable Patterns
Critical: Do NOT create skills for specific cases. Abstract to general patterns.
Ask yourself:
- What CATEGORY of problem was solved? (not the specific instance)
- What would this look like with different data/context?
- Would this skill be useful in other projects?
Abstraction levels (from bad to good):
| Too specific (BAD) | Good abstraction |
|---|---|
| "Seed users from client Excel" | "Import spreadsheet data into Rails" |
| "Parse names into fields" | (implementation detail, not a skill) |
| "Fix pytest in project X" | "Configure pytest for monorepos" |
| "Add dark mode to app Y" | "Implement theme switching in React" |
Rules:
- Remove project names, organization names, specific entities
- Focus on the TECHNIQUE, not the specific data
- If something is just an implementation detail (name parsing, date formatting), it's not a separate skill
- One dialog = usually one skill (the main workflow), not multiple micro-skills
3. Extract Context-Specific Details
Depending on the task type, look for:
Development tasks:
- Commands and flags that worked
- Versions and compatibility (what works with what)
- Configuration that was needed
- Code patterns and architectural decisions
- Debugging process (how the root cause was found)
- Tool/library choices and why
Research/analysis tasks:
- Sources that proved useful
- Search strategies that worked
- How to validate findings
Process/workflow tasks:
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.
- 8d ago First seen · 169 lines · 57 tokens per session scan A c8e900ab38d1
chat-to-skill is a skill published in the GitHub repository dannote/dot-pi (51 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 1,112 once invoked, about $0.0003 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
a0-development
Development guide for extending Agent Zero from current source and DOX. Use for framework architecture, tools, extensions, API/WebUI handlers, agent profiles, prompts, skills, projects, runtime boundaries, and contribution workflow. Load the focused reference files before giving implementation guidance.
temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or…
cafleet
Interact with the CAFleet message broker and supervise CAFleet member teams. Use when an agent needs to register as a member, send/receive messages, poll inbox, acknowledge messages, or discover other members; or when a Director is about to spawn, monitor, health-check, or recover a stalled team of CAFleet members…
speq-implement
Orchestrate implementation of a reviewed plan: task breakdown, TDD sub-agents, code review, and verification report. Use when the user asks to implement, build, or execute a plan under specs/plans/ — after /speq-plan, before /speq-record. Arg: .
speq-plan-pr
Headless, non-interactive version of /speq-plan for CI or agent-driven runs. Plans a feature without a live interview, commits the result to a feat/plan-name branch, and opens a draft PR. If a decision genuinely needs a human, it persists the partial plan and open questions and asks in a PR comment instead of…
speq-implement-pr
Headless follow-up to /speq-plan-pr. Continues a plan on its feat/plan-name branch and runs it end-to-end: implements via /speq-implement, bumps the version, commits and pushes, runs the real test suites, records only if green, then opens/updates the PR and marks it ready. Resumes from the PR Lifecycle checkpoint in…