Loading...
Loading...
Found 215 Skills
A retrieval and Q&A assistant for local knowledge base directories. Core processes: (1) Hierarchical index navigation (2) When encountering PDF/Excel files, must first read references to learn processing methods (3) Retrieve after processing files. Use a combination of grep, Read, pdfplumber, pandas for progressive retrieval based on file types, avoiding full-file loading. Used when user questions involve "answering questions/retrieving information/searching for materials from knowledge base directories".
Detect stale and potentially outdated documents in your Yuque knowledge bases by analyzing update timestamps and content freshness signals. For personal/individual use — scans your own repos.
Guide for using the `paper` CLI tool — a local academic paper management system with AI-powered vector search. Use this skill whenever the user wants to manage academic papers, create knowledge bases, add PDFs to a knowledge base, search papers semantically, configure embedding models, or manage literature metadata and notes. Also trigger when the user mentions "paper" CLI, knowledge bases for research, literature management, or wants to query their paper collection. Even if the user just says something like "add this PDF" or "search my papers" in a project that uses paper-manager, this skill should activate.
Update Knowledge Base — Execute doc-updater, code-reviewer, and learn-eval in sequence to solidify the changes from this session into documents and knowledge.
LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)
Enforce consistent tagging across the Obsidian wiki using a controlled vocabulary. Use this skill when the user says "fix my tags", "normalize tags", "clean up tags", "tag audit", "what tags should I use", "tag taxonomy", or whenever you're creating or updating wiki pages and need to choose the right tags. Also trigger when the user asks about tag conventions, wants to add a new tag to the taxonomy, or says "my tags are a mess". Always consult this skill's taxonomy file before assigning tags to any wiki page.
Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki, second brain, or knowledge base.
Generate creative prompts and thought experiments from wiki content. Use when the user wants inspiration, says "spark", "what if", "give me ideas", "what should I explore next", or wants creative prompts from their wiki, second brain, or knowledge base.
Document finalized technology selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent documents. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four types: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively push when important choices are made after feature-design or issue-analyze, or when the user says "record decision", "archive technology selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive under-discussion solutions.
Brain knowledge base operations. The core read/write cycle: brain-first lookup, read-enrich-write loop, source attribution, ambient enrichment, back-linking. Read this before any brain interaction.
Search for new products and technologies through multiple channels, cross-verify the information, and store it in the knowledge base. Use this when users mention "latest information", "new products", "search for information", "look up information", or "learn about XX".
Help users add knowledge base documents to Runway Characters for domain-specific conversations