「wiki」の検索結果

Audit a second-brain vault for structural problems and repair them: broken wikilinks, orphan pages, empty stubs, frontmatter that violates the schema, near-duplicate pages, and stale index entries. Use this skill whenever the user asks to lint, clean, audit or check the health of their vault, says pages feel messy or links are broken, after a large bulk import, or when a scheduled maintenance run fires. Do NOT use for ingesting new sources, for answering questions from the vault, or for rewriting page content that is structurally fine but reads badly.

日本語の概要は準備中です。原文の説明を表示しています。

Set up or update a project in the vault: the four-stage folder pipeline, a project-scoped CLAUDE.md with one goal, and links to the concept pages it depends on. Use this skill when the user starts something new they will work on over time, says "create a project", "set up a folder for X", or asks to define the goal and structure of ongoing work. Do NOT use for one-off tasks, for wiki pages about a topic, or for scoping an existing project down to work in it.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "suggest Grokipedia article," "Grokipedia citation," "Grokipedia listing," "AI search citation," "GEO visibility," or "Grokipedia optimization." For multi-platform parasite SEO strategy, use parasite-seo. For broad AI search visibility, use generative-engine-optimization.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.

日本語の概要は準備中です。原文の説明を表示しています。

Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech writing, knowledge base, wiki, runbook, README, internal docs, doc audit, doc maintenance, stale docs, where do we document. Also triggers when the team is repeatedly answering the same questions or when onboarding takes too long.

日本語の概要は準備中です。原文の説明を表示しています。

Confluence expert for spaces, knowledge bases, documentation, page layouts, macros, templates, and Jira-Confluence integration. Use for documentation strategy, space architecture, content organization, and collaborative knowledge management.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and repair an internal knowledge base — staleness, ownership gaps, orphans, duplication, and findability. Use when the wiki is untrusted, docs are out of date, nobody owns pages, or search returns the wrong answer.

日本語の概要は準備中です。原文の説明を表示しています。

Audit brand entity facts AI engines trust: Wikidata, Knowledge Panel. "is our Knowledge Panel accurate"

日本語の概要は準備中です。原文の説明を表示しています。

Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse."

日本語の概要は準備中です。原文の説明を表示しています。

Graph objects from pathway topology derived from KEGG, Panther, PathBank, PharmGKB, Reactome SMPDB and WikiPathways databases.

日本語の概要は準備中です。原文の説明を表示しています。

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

日本語の概要は準備中です。原文の説明を表示しています。

Skills wiki intro - mandatory workflows, search tool, brainstorming triggers

日本語の概要は準備中です。原文の説明を表示しています。

千问AI平台（Qianwen AI Platform / DashScope）官方文档离线知识库，用于检索并回答模型选择、API Key、OpenAI 兼容接口、DashScope SDK、文本与多模态生成、图像/视频/语音、Realtime API、Embedding、Reranking、Function Calling、MCP、批量调用、计费、Token Plan、API/SDK/CLI 参考和模型更新等问题，也可基于官方文档生成示例代码与排障建议。当用户提到千问AI平台、Qianwen AI Platform、DashScope、通义千问 API、百炼 API、DASHSCOPE_API_KEY 或具体千问/万相模型接入时使用；千问聊天产品的一般使用、模型原理论文解读或无关的阿里云产品问题不使用。

日本語の概要は準備中です。原文の説明を表示しています。

LlamaIndex 官方用户文档离线知识库，用于检索并回答 LlamaIndex Python 框架的安装、RAG、数据加载、索引、检索与查询、Agent、Workflow、模型、Embedding、向量库、评估、可观测性、部署、LlamaCloud 和 LlamaParse 等问题，也可生成有文档依据的示例代码与排障建议。当用户提到 LlamaIndex、llama-index、LlamaParse、VectorStoreIndex、QueryEngine、Retriever、AgentWorkflow 或相关集成用法时使用；纯源码贡献、内部实现审查或与 LlamaIndex 无关的通用 AI 问题不使用。

日本語の概要は準備中です。原文の説明を表示しています。

Design or audit a repo-local markdown knowledge graph with wiki links, source-code backlinks, drift checks, and searchable sections. Use when AGENTS.md/CLAUDE.md is too flat for a large codebase or when a custom harness needs durable structured project memory.

日本語の概要は準備中です。原文の説明を表示しています。

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

日本語の概要は準備中です。原文の説明を表示しています。

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.

日本語の概要は準備中です。原文の説明を表示しています。

Intent-driven knowledge-store and Run knowledge lifecycle management — read-only audit/prune reports, stage candidates (with signal recording), review/resolve/promote candidates, harvest artifacts, or manage wiki/domain knowledge.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain bounded, durable AI project memory in a repository's docs/ai/ pack. Use when Codex or Claude Code needs to create, read, update, or audit project memory (project-card, architecture, diagrams, runbook, handoff, gotchas, ADRs), install AGENTS.md memory rules, or sync a lightweight central LLM Wiki project entity for user-owned projects.

日本語の概要は準備中です。原文の説明を表示しています。

Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via MCP server (recommended) or API token authentication (fallback).

日本語の概要は準備中です。原文の説明を表示しています。

Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs → roadmap → backlog), continuous discovery, backlog craft (epics, INVEST stories, acceptance criteria), prioritization frameworks (RICE, MoSCoW, Kano, WSJF), sprint delivery, metrics (North Star, AARRR), stakeholder management, and anti-patterns. The PO/PM owns what gets built, in what order, and why — including the end-to-end user flows and user journeys. Use when scoping a product or feature, decomposing an idea into outcomes/epics/stories, prioritizing a backlog, defining an MVP, mapping user journeys, measuring success, or saying no to a stakeholder. Pairs with super-ui-ux-design, which owns how each screen looks and behaves.

日本語の概要は準備中です。原文の説明を表示しています。

Complete UI/UX design capability — a wiki-style knowledge map of design theory (UX laws, Nielsen heuristics, usability, visual hierarchy, typography, contrast/WCAG, design systems, aesthetics-vs-conversion) fused with a hands-on execution playbook for building distinctive, production-grade frontend interfaces. Use when designing or building any UI (websites, landing pages, dashboards, components, apps), reviewing or critiquing UI/UX, diagnosing why a design doesn't convert, or styling/beautifying web interfaces. Grounds every visual decision in UX principles and avoids generic AI aesthetics.

日本語の概要は準備中です。原文の説明を表示しています。

Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.

日本語の概要は準備中です。原文の説明を表示しています。

Build or revise private, cited Markdown notes from the user's WeChat history in the current agent session. Use for a maintained personal wiki or incremental notes; use greenbubbles-context for a one-off lookup or summary.

日本語の概要は準備中です。原文の説明を表示しています。