문서·Office 스킬

Spatial dimensions of political power, state sovereignty, territorial conflict, borders, international governance, and critical geopolitics. Covers classical geopolitics (Mackinder, Ratzel, Mahan), critical geopolitics (Said, O Tuathail), state territory and sovereignty, border theory, international organizations and governance, electoral geography, and postcolonial perspectives on power and space. Use when reasoning about territorial disputes, borders, international relations, state power, colonialism and its legacies, or the politics of geographic representation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Before dispatching a multi-agent team, run a spectral diagnostic on the proposed communication graph and emit a (ρ, Δ, κ) coordination signature plus a pass/fail verdict against per-task-class thresholds. Builds the row-stochastic operator P from the team graph, computes the successor representation M = (I − γP)⁻¹, and ranks the topology for robustness (κ, condition number), consensus (Δ, spectral gap), and drift (ρ, spectral radius). Per Parks & Alharthi (arxiv 2605.11453), rank order on (κ, Δ, ρ) predicts coordination quality pre-execution with rank correlations of 1.0 / 0.5 / −1.0. Triggers: "dispatch the team", "team topology check", "before running the agents", "is this team configuration OK", "team pre-flight".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Remove AI-isms and artificial language patterns from text. Makes documentation, comments, commit messages, and prose sound more natural and human. Based on Wikipedia's "Signs of AI writing" patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Documentation and orchestration for the bmorphism/ies flox environment toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CatColab Ologs (Ontology Logs) - category-theoretic knowledge representation where objects are concepts and morphisms are functional relationships. Foundation for database schemas and conceptual modeling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to create custom Remotion transitions, asks about "cool transitions", "cinematic transitions", "striped transitions", "glitch transitions", "custom TransitionPresentation", or wants to build scene-to-scene transitions in Remotion beyond the built-in library. Also triggers for "how to make transitions in Remotion", "custom transition", "high-energy transitions", "energy transitions", "branded transitions".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess whether the documentation in src/site/markdown/ adequately covers the Java SDK functionality.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reads or converts documents in a research workflow, including PDF, Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, and CSV. Chooses direct reading or conversion, selects a converter from document structure, and decides whether the Markdown is tracked or temporary. Use when a document must be read, quoted, summarized, searched, extracted, or added to a source library. Scanned documents go to vlm-ocr and bulk intake to research-repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft commit titles and optional commit bodies using the workspace commit naming convention. Use when the user asks for a commit message, commit text, commit title, or wants commit wording in the format `chore|bugfix|feature - <issue_id(s)> <short description>`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to "add an example", "write a tutorial", "document a new workflow example", or when creating a new worked example under `docs/source/examples/`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user asks to "write documentation", "add a doc page", "update RST files", "add a tutorial", or when writing or editing Sphinx RST documentation for StreamFlow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the primary outcome is authoring, rewriting, summarizing, or validating user-facing documentation without implementation comparison or required source attribution, including READMEs, tutorials, API docs, GitLab Markdown, source-faithful summaries, and audience-specific prose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Summarize a supplied URL from fetched content with source locations, acquisition coverage and explicit access failures. Use for articles, documentation, API references and web pages; preserve version, author attribution and uncertainty in the requested output format.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the primary outcome is creating a new portable Agent Skill directory from one local documentation file, documentation directory, or Git repository, including mixed text and capability-gated binary sources that require exhaustive source-to-output accounting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MkDocs documentation project reference covering CLI commands, mkdocs.yml configuration, Material theme setup, and plugin integration. Bundled references include complete CLI parameters, all mkdocs.yml settings with valid values, Material theme customization options, and plugin configs for mkdocstrings, mermaid2, mkdocs-gen-files, mkdocs-literate-nav, and mkdocs-typer2. Use when initializing a MkDocs site, configuring mkdocs.yml, customizing the Material theme, integrating plugins, building static docs from Markdown, or generating API documentation from Python docstrings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze, improve, or represent processes across a file or directory by delegating to process-siren. Uses the same semantic model and validation loop as single-process work; Mermaid is produced when it is the useful concise representation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add automated documentation updater to any Claude skill. Creates a Python sync script that downloads upstream docs, processes markdown for AI consumption, and maintains local cache with configurable refresh. Collects template variables, then delegates implementation through 5-phase workflow. Use when adding auto-updating reference documentation to plugins or skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plugin creator documentation index. Load when needing to read about plugin validation error codes, skill creation, agent creation, or plugin structure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate a completed plugin refactor against its task evidence, baseline assessment, documentation, and current validators. Use after implement-refactor or when deciding whether refactoring is complete.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review changed user-interface or CLI presentation behavior for accessibility failures. Use for an independent accessibility perspective on a defined change set.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Synchronize existing documentation with an observed code/configuration/API change while preserving each document's purpose and authority. Use after implementation changes can make documentation stale, incomplete, or internally inconsistent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.