475 skills · sorted by relevance
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.
Answer questions using Paperclip wiki pages and original sources, with citations for each claim. Identify missing information clearly and, with user approval, save useful comparisons or explanations as linked wiki pages for future reference.
Maintain a local company wiki by incorporating source material, answering questions, and organizing navigation. Preserve original sources while keeping citations, links, and update logs, with project summaries that separate current status from lasting knowledge.
Drive the AgentWiki knowledge platform via its CLI (`@aiagentwiki/cli`, command `agentwiki`) and MCP server (`https://api.agentwiki.cc/mcp`). Use this skill whenever the user mentions AgentWiki, agentwiki.cc, app.agentwiki.cc, the `agentwiki` CLI, the `@aiagentwiki/cli` npm package, the AgentWiki MCP server, or asks to create/list/search/share/publish documents, manage folders or tags, upload files or images, deploy static sites, traverse a knowledge graph, or query their AgentWiki workspace from the terminal or as an AI agent. Triggers include phrases like "agentwiki login", "aw_… API key", "create a doc on agentwiki", "search my wiki", "publish to agentwiki", "agentwiki MCP", or any task that would otherwise require opening app.agentwiki.cc manually.
The English summary is being prepared. Showing the original description.
Browse Feishu knowledge spaces, locate pages from wiki links, and organize pages through creation, moves, and renaming. Resolve the linked content so an appropriate document or content tool can read or edit it.
Maintain a memory wiki for use in Obsidian by organizing note links, stable filenames, and metadata at the top of files. Repair links after renames and check available tools before using Obsidian commands.
Search an existing repository OpenWiki to clarify architecture and dependencies, or create and update its documentation. Pages explain system behavior using source evidence, with a resumable workflow that tracks progress one page at a time.
Maintain an OpenClaw memory wiki using original sources and stored notes. Update existing pages, preserve human-written sections, and check for contradictions, missing source information, and unresolved questions after meaningful changes.
Fill unfinished research-wiki paper pages using summaries and abstracts from external sources. Organize each paper’s problem, method, results, limitations, and reusable ideas while preserving existing content by default and recording which source supplied the information.
Refresh an LLM Wiki index against the pages that actually exist. Add missing entries, remove entries for deleted pages, preserve custom categories, and log change counts while leaving page bodies untouched.
Turn bundled Paperclip issues, comments, and documents into readable wiki updates covering project purpose, current progress, decisions, risks, and next actions, while preserving existing knowledge and citing the supporting activity.
Build a connected Markdown Wiki from documents, notes, transcripts, research, and code. Organize knowledge by subject, attach evidence to claims, maintain a navigation index, and integrate new material into existing pages while preserving disagreements and context.
Audit an LLM Wiki for conflicting or outdated claims, broken links, missing concept pages, weak sources, and index inconsistencies. Return findings grouped by severity with evidence and suggested fixes, leaving page content unchanged.
Turn a captured source document into linked LLM Wiki pages for sources, entities, concepts, and combined insights. Update the index and log, preserve the original material, and flag contradictions with existing knowledge instead of silently replacing it.
Build a built-in connector that brings a new information source into OpenWiki. It guides the choice between an existing MCP server connection and custom code, covering authentication, incremental fetching, stored data, and tests.
Assess a brand’s presence on YouTube, Reddit, Wikipedia, LinkedIn, and other sources relevant to AI search. Review mentions, official profiles, and discussion sentiment, then produce a weighted authority score and recommendations for each platform.
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.
Turn documents into a growing Markdown wiki and a knowledge graph, a map of entities and their relationships. Preserve source text, update linked pages as new material arrives, and answer questions with supporting evidence.
Create and review company procedures and operational guides, then audit internal wikis for outdated pages, missing owners, broken connections, and inconsistent terminology. Produce structured drafts, step checks, and a prioritized list of documents to improve.
Run repeatable, read-only checks on an Obsidian wiki to find broken or ambiguous links, isolated pages, missing metadata, empty sections, outdated index entries, and source-record issues. Review findings with paths, line numbers, and counts.
Build and maintain a persistent, interlinked markdown wiki (second brain / research notebook / personal knowledge base) from raw sources. Use this skill when the user wants to ingest an article / paper / note / URL / PDF into their wiki, ask a question against their wiki, lint/health-check their wiki, or set up a new wiki from a folder. Triggers include phrases like "add this to my wiki", "ingest this", "file this article", "update my notes with this", "what does my wiki say about X", "health-check my wiki", "find stale/orphan pages", or any workflow involving a `raw/` source folder, `wiki/` markdown folder, `index.md`, or `log.md`. Compatible with Obsidian vaults.
The English summary is being prepared. Showing the original description.
Turn a codebase into a structured wiki with architecture notes, module references, and setup instructions. Generate Mermaid diagrams, which describe diagrams as text, and link explanations to the source files they document.
Build and maintain a Markdown knowledge store with source links for individual claims. Use Git checks to detect changes in the code a page describes, and archive outdated pages while preserving their history.
Keep project decisions, debugging notes, and session discoveries in a lasting Markdown wiki. Organize pages with tags and categories, connect related notes with links, and retrieve information through keyword searches.