712 skills · sorted by relevance
Turn a large codebase spanning multiple repositories or services into a structured knowledge base. It documents architecture, business rules, and dependencies, links conclusions to source lines, labels confidence in relationships, and supports incremental updates.
Use this skill when setting up, configuring, or managing Salesforce Lightning Knowledge — enabling the feature, designing record types on Knowledge__kav, configuring Data Categories for organization and visibility control, setting up publishing workflows, and layering approval processes. Trigger keywords: Lightning Knowledge setup, Knowledge article record types, Data Category visibility, Knowledge publishing workflow, Knowledge__kav configuration. NOT for converting Classic Article Types to Lightning — use admin/knowledge-classic-to-lightning. NOT for bulk-loading articles from an external help center — use data/knowledge-article-import. NOT for sizing the taxonomy itself (how many groups, how deep) — use architect/knowledge-taxonomy-design.
The English summary is being prepared. Showing the original description.
Organize knowledge notes with links that explain their relationships, search saved information, review conflicting claims, and prepare weekly digests. Retrieve earlier work sessions and conversations by topic or date to recover context before continuing a task.
Save, organize, synchronize, and retrieve documents, conversations, and project information across local files, memory tools, knowledge repositories, and databases. Check for duplicates before storing information and choose a suitable home for each type of knowledge.
Synthesize OpenViking knowledge bases or document collections into topic-based Markdown pages that explain trends, changes, comparisons, and implications. Keep conclusions traceable to source evidence, distinguish facts from inferences, and preserve disagreements and uncertainty.
Create, validate, and enrich Open Knowledge Format (OKF) bundles — the open spec for representing organizational knowledge as markdown files with YAML frontmatter. Use when the user mentions 'OKF', 'Open Knowledge Format', 'knowledge bundle', 'OKF bundle', 'create a knowledge base for agents', 'validate OKF', 'convert to OKF', 'enrich knowledge docs', 'agent-readable knowledge', 'LLM wiki', 'knowledge catalog', 'kcmd', or wants to structure knowledge as markdown files for AI agent consumption. Also use when the user has a directory of markdown files and wants to make them interoperable or conformant with the OKF standard. Even for simple requests like 'make this folder OKF conformant' — the skill has critical structural rules the agent needs.
The English summary is being prepared. Showing the original description.
Build focused knowledge bases from claude-mem observations, filtered by topic, project, date, or file. Load selected records into an AI conversation to ask contextual follow-up questions about past decisions, fixes, and work patterns.
Organize articles, documents, and insights from conversations into a personal Markdown wiki. Maintain source references, links between related topics, an index, and an activity log, then answer questions using the knowledge already collected.
Crawl linked pages within a chosen website scope and collect clean text, Markdown, or HTML with page metadata. Use the resulting records as source material for AI search systems or chatbot knowledge bases.
Access TeamAI workflows for sharing skills, rules, documents, and environment settings across AI coding tools. This entry skill loads version-matched guidance for team setup, synchronization, codebase knowledge, and sharing lessons from a session.
Migrating Classic Knowledge (KnowledgeArticleVersion / Article Types) to Lightning Knowledge (Knowledge__kav with record types): article-type-to-record-type mapping, multi-language translation preservation, data category re-architecture, file attachment porting, version and publication-state retention, channel visibility translation, and downstream Case Feed / Community / Bot rewiring. NOT for new Lightning Knowledge setup or editorial publishing workflow design (use admin/knowledge-base-administration).
The English summary is being prepared. Showing the original description.
Agent fallback for CDelayedCall2_CServerSideClientBase_UpdateAcknowledgedFramecountCall_vtable (auto-generated, category: func). Locate CDelayedCall2_CServerSideClientBase_UpdateAcknowledgedFramecountCall_vtable in the CS2 engine module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CDelayedCall2_CServerSideClientBase_UpdateAcknowledgedFramecountCall_vtable, CDelayedCall2_CServerSideClientBase_UpdateAcknowledgedFramecountCall_vtable
The English summary is being prepared. Showing the original description.
Turn a founder’s business vision into linked Markdown files through a phased interview covering strategy, finance, sales, operations, and governance. Build a company knowledge bundle that people and AI agents can read, with progress tracking and decision history.
Find and synthesize official Google developer documentation for platforms including Google Cloud, Gemini, Android, and Firebase. Retrieve command syntax, API details, permissions, and product comparisons through Developer Knowledge, then turn the findings into practical technical answers.
Build and maintain a Markdown knowledge base from source materials, with linked pages and traceable evidence. Use accumulated knowledge to answer questions, preserve reusable research, and check for conflicting claims, outdated information, broken links, or missing index entries.
How to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedures live elsewhere: ingest in the platform `open-knowledge` skill, research and consolidate as their own sibling skills in this pack. Complements the platform `open-knowledge` skill; does not replace it.
The English summary is being prepared. Showing the original description.
How to work in a Codebase Wiki project (the `codebase-wiki` starter pack): an agent-authored, source-grounded wiki of the surrounding codebase. Read when the project has a `wiki/` knowledge base with `architecture/`, `modules/`, `flows/`, `concepts/`, and `guides/` sections plus `wiki/OVERVIEW.md`, or when asked to generate or refresh a wiki of this codebase. Carries the per-folder rules and freshness + log discipline, summarizes the audience/depth knobs and source-reference convention, and bundles the full generate/refresh procedure in `references/`. Complements the platform `open-knowledge` skill; does not replace it.
The English summary is being prepared. Showing the original description.
Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI', 'create knowledge base', 'set up project context', or 'configure AI context'.
The English summary is being prepared. Showing the original description.
Generate and maintain AI-readable markdown documentation for a codebase in docs/. Use this skill whenever the user asks to document their codebase, generate project docs, create architecture docs, update documentation after code changes, build a knowledge base for AI agents, create onboarding docs, map out a codebase, or explain a project structure. Also trigger when users say things like "document this repo", "create docs for my project", "update the docs", "write architecture documentation", "help AI understand my code", "generate a codebase overview", or "maintain docs". This skill is specifically about creating structured markdown files in a docs/ directory that serve as a knowledge base — NOT about writing inline code comments, README files, or API reference docs from docstrings.
The English summary is being prepared. Showing the original description.
Turn a structured LLM wiki into an interactive knowledge graph. It maps articles, topics, and sources, then adds entities and inferred relationships to help readers explore connections beyond the wiki’s explicit links.
Build systems that use Pinecone to find documents for AI answers or retain agent memories across sessions. Guides index setup, data loading, meaning-based and keyword search, memory separation, and end-to-end checks.
Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.
Choose the right WeKnora command to answer questions from a knowledge base or retrieve source passages. Covers cited answers, custom agents, document searches, and continuing a conversation through the command-line tool.
Set up a lasting wiki knowledge base for a NanoClaw group. The skill helps define its topic, organize source files and wiki pages, and establish workflows for adding material, answering questions, and checking the wiki.