Loading...
Loading...
Found 999 Skills
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.
Fetch and compile arXiv papers on LLMs, autonomous agents, and AI infrastructure into scored, grouped research digests. Stores digests at ~/.aibtc/arxiv-research/digests/. No API key required.
Append project fragment knowledge that is "too short to warrant a separate file but needs to be known by AI every time" to fixed sections of AGENTS.md / CLAUDE.md — such as special compilation flags, services that must be started before running, path pitfalls, command aliases, and environment variable conventions. Triggers: When the user says "make a note", "add to AGENTS", "save to CLAUDE.md", "the project requires X to compile", "must do Y every time from now on", or just encountered a project-specific setting that can be explained in one sentence.
Use when the user wants to write or publish a WeChat Official Account article — they share rough thoughts, a draft, or notes and ask for help polishing, generating a cover image and explanatory illustration, or preparing the article for upload to mp.weixin.qq.com. Triggers include "Write a WeChat article", "Official Account", "Polish", "Cover Image", "Publish to Official Account", "/wjs-publishing-wechat".
Compile durable knowledge into interlinked-markdown stores the "karpathy method" way — atomic files, [[wiki-links]], a maintained index. Use after producing research, intel, a digest, a learned non-obvious fact, or finishing any knowledge-shaped task, BEFORE you close it. Also when asked to "save this", "write this to the wiki", "update the wiki/memory", "log this finding", "structure this knowledge", or "follow the karpathy method".
AI-powered SVG article illustration generator supporting three output modes: dynamic SVG, static SVG, and PNG export. Use this skill when users need to generate illustrations for articles, create SVG graphics, convert SVG to PNG, or mention "article illustration generation" or "create illustrations".
Create and edit presentation slides using Slidev framework when user requests slides, presentations, or deck modifications
Write a new doc-site page (guide, tutorial, reference, concept) following the project's docs conventions. Use when user says 'write a doc', 'add a page to the docs site', 'create a guide for X', 'write a tutorial', 'document this concept', or 'add reference for our API'. Do NOT use for feature-specific end-user docs (use document-feature), ADRs (use document-decision), or CLAUDE.md updates (use create-or-audit-claude-md).
Recent community and social trend research over the last 30 days. Use when the brief asks what people are saying now, recent sentiment, community reactions, social proof, launch reaction, trend scan, or last-30-days context.
Run a health check on existing memory (the wiki substrate) and goal artifacts. Use this when the user wants to lint the wiki, health-check the knowledge base, find orphan pages, spot broken or missing cross-links, clean up stale claims and unresolved wikilinks with safe local fixes, consolidate a legacy root `overview.md` into `index.md`, or health-check goal artifacts. Not for adding new material; use /loam::adding-to-memory or /loam::learning-from-session for that.
Comprehensive skill for the `kb` CLI and the Karpathy Knowledge Base pattern. Covers the full KB lifecycle — topic scaffolding, multi-source ingestion (URLs, files, YouTube, bookmarks, codebases), wiki article compilation, cross-article querying with file-back, lint-and-heal passes, QMD indexing, and hybrid search. Also covers codebase-specific analysis via inspect commands for complexity, coupling, blast radius, dead code, circular dependencies, symbol/file lookups, backlinks, and code smells. Use when working with kb CLI commands, knowledge base workflows, code vault generation, code graph analysis, code metrics inspection, wiki compilation, or the ingest-compile-query-lint cycle. Do not use for general code review, linting, formatting, building Go projects, or writing application code.
Generates a human-readable security review packet compiled from confirmed findings and exploit chains. Use at the end of a review cycle to produce stakeholder-facing documentation. Don't use for auditing code or verifying patches directly.