libtorrent
libtorrent Documentation Assistant
You have access to a local mirror of libtorrent.org documentation and blog posts, stored as markdown. Use it to give accurate, detailed answers about libtorrent.
The docs live at: ~/github/soup/libtorrent-docs/
How to find information
-
Start with the indexes. Read the relevant index to find the right file:
docs/index.md— all documentation pages (~47 files)blog/index.md— blog posts from 2011–2022 (~31 posts)
-
Read the specific file. Once you've identified the relevant doc or blog post, read it. Don't guess from titles alone — the content is right there.
-
Check images when referenced. Diagrams and graphs are saved locally in
images/and can be read directly. If a doc references a figure, look at it — it often contains information the text doesn't.
Quick reference for common topics
These are the most frequently useful files:
More from s0up4200/skills
mobile-adapt
Use when a user wants a site, app, screen, flow, dashboard, or full project adapted for phones or mobile web, or mentions responsive/mobile-first/iPhone/iOS Safari/touch/safe-area/landscape/keyboard issues. Also use for mobile audits, mobile regressions, small-screen layout fixes, bottom navigation redesigns, form/table/chart adaptation, or iPhone-specific usability work.
12claude-code-docs
Search and reference official Claude Code documentation locally. Use whenever the user asks about Claude Code features, configuration, hooks, MCP, settings, permissions, CLI flags, IDE integrations, plugins, skills, agent teams, scheduled tasks, sub-agents, custom agents, worktrees, session management, Desktop app features, or any other Claude Code capability. Also use when you need to look something up yourself mid-task — checking hook schemas, CLI flags, environment variables, settings format, etc. Prefer this over web fetching for Claude Code docs. Claude Code evolves fast — features like custom agents (.claude/agents/), session forking (/branch), /batch, live app preview, and worktree support are newer and not reliably in model training data, so always check the docs rather than guessing.
7release-tag
Create and push a signed git release tag. Use this skill when the user says "tag a release", "new release", "cut a release", "bump version", "release tag", "tag version", "push a tag", or any variation of wanting to create a new version tag. Also use when the user types "/release-tag" or "/release".
6retro
>-
3platform-docs
Search and reference official Anthropic platform documentation locally. Use whenever the user asks about the Claude API, Anthropic SDKs (Python, TypeScript), REST API endpoints, models, pricing, tool use, computer use, MCP server protocol, prompt engineering, extended thinking, prompt caching, vision, batch processing, Agent SDK, embeddings, streaming, structured outputs, citations, context windows, token counting, files API, PDF support, multilingual support, model deprecations, rate limits, error codes, or any other Anthropic platform capability. Also use when you need to look up API details yourself mid-task — checking request/response schemas, SDK method signatures, authentication, or endpoint parameters. Prefer this over web fetching for Anthropic API and platform docs. NOT for Claude Code (the CLI tool) — use claude-code-docs for that.
2emotional-awareness
>-
1