글쓰기·창작 스킬

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

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

Design intentional internal link graphs for SEO, UX, and LLM-readable sites. Use this skill when the user asks for links between short briefs, longform articles, topics, projects, author pages, breadcrumbs, source trails, related stories, orphan-page checks, overlink checks, anchor intent, or validation that a link graph reinforces the canonical content model without creating duplicate story bodies or hidden links.

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

Specialized prompt-building methodology for content and communications tasks. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for writing, editing, content strategy, copywriting, audience analysis, editorial evaluation, cross-channel adaptation, and persuasion design. Use when building a Claude prompt or system prompt for content creation, editorial workflows, or communications tasks. Trigger on: "build a prompt for writing," "prompt for content strategy," "prompt for copywriting," "prompt for blog posts," "prompt for email sequences," "system prompt for editorial," "prompt for messaging framework," "content brief prompt," "prompt for audience analysis," "prompt that produces better content." Do NOT use for writing content directly — this Skill builds prompts that produce better content. Do NOT use for evaluating or scoring existing prompts — use rootnode-prompt-validation if available. Do NOT use for general prompt compilation — use rootnode-prompt-compilation if available.

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

Measures the work in a code repo as deeds (caps, fixes and tends) by running the bundled `deeds` CLI over the commit history, for this repo or any GitHub repo, over any time window. Reports totals, a week-by-week trend, a per-author breakdown and the named caps, and explains what the numbers mean.

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

Use when the user says remember this or settles one durable fact. Not for remote, credential, publish, deploy, or irreversible changes.

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

Use when the user asks to remove a session or note from recall, or to unforget or list exclusions. Not for remote, credential, publish, deploy, or irreversible changes.

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

Use when a user requests the reasoning behind one matched session by query or handle. Not for peer transfer: use history-sync. Not for store registration: use history-source-registry.

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

Use when a coding-agent session store is added or its format drifts, to document its layout, roles, quirks. Not for recalling a session: use history-recall. Not for peer transfer: use history-sync.

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

Use when the user requests memory transfer to or from a named peer. Not for recalling a session: use history-recall. Not for store registration: use history-source-registry.

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

Use when a user asks to audit what recall fed agents. Not for source or remote-system changes.

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

Use when a human directly requests review and publication of an existing diff or delegated work. Not for merging pull requests, force pushes, history rewrites, or deployment.

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

Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.

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

Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push-pr.

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

Use when a user wants agent setup graded from conversation history. Not for skill fixing: use agent-surface-forge. Not for security scanning: use skill-scanner.

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

Apply WIT (Writing Is Thinking) as a human–LLM collaborative scientific reasoning skill for scientific question formulation, finding-driven research planning, next-experiment selection, Results or Discussion review, claim–evidence and reviewer stress tests, manuscript logic audits, deadline closure, and researcher growth. Use when the user invokes WIT or asks for these question-driven scientific reasoning workflows; do not use for generic copyediting, summarization, or literature search alone.

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

UX/マーケティング向けのユーザーペルソナを、5つの専門エージェントチームで作成するスキル。 ペルソナ設計、ユーザーリサーチ、ナラティブ執筆、バイアスレビュー、データ検証の 5観点からペルソナをディスカッション型で議論・作成し、Markdownドキュメントとして出力する。 data-critic がライブモデレーターとして矛盾を検出・収束を判定する。 コンテキストファイルで過去のセッションを引き継げる。 Use when: ユーザーペルソナを作りたい、ターゲットユーザーを定義したい、 ペルソナシートを作成したい、UXリサーチ用のペルソナが必要、 マーケティング用のターゲット分析をしたい。 Triggers: "ペルソナ", "persona", "ターゲットユーザー", "target user", "ユーザー像", "ユーザー定義", "user profile", "ペルソナシート", "ターゲット分析", "ユーザーセグメント", "customer profile"

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

ユーザーストーリーを可視化する専門スキル。6つの専門エージェントチームで、 ジャーニーマップの分析から Pencil (.pen) ビジュアル出力まで一気通貫で実行する。 プロダクト情報とターゲットユーザーを入力し、認知→検討→初回利用→習慣化→推薦の 5フェーズで行動・思考・感情・接点・機能・課題・機会・Devアクションを構造化し、 Markdownドキュメントと Pencil ビジュアルジャーニーマップを出力する。 離脱トリガー分析を強化し、ペインポイントと機会を視覚的に強調する。 ペルソナファイルがあれば自動読み込み、なければ手動入力でも動作する。 Use when: ジャーニーマップを可視化したい、ユーザー体験を図で表現したい、 カスタマージャーニーをビジュアル化したい、離脱要因を分析したい、 UXフローを .pen ファイルで出力したい。 Triggers: "ジャーニー", "journey", "ジャーニーマップ", "journey map", "ユーザー体験", "user journey", "UXフロー", "体験設計", "カスタマージャーニー", "customer journey", "可視化", "visualize", "user story", "ユーザーストーリー", "離脱分析", "drop-off"

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

Use when planning, auditing, or speccing a video's motion and visual craft: shot lists, storyboards, color scripts, transitions, easing, kinetic typography, pacing, retention, or animation principles. Triggers: 'video plan', 'shot list', 'storyboard', 'color script', 'motion spec', 'fix the pacing', 'explainer/demo/brand video'. For the spoken words themselves, use script-writer-skill; for in-code UI motion, use frontend-design.

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

Operator-side analysis of historical ML experiment PRs in Senpai research tracks. Use this skill whenever the user asks to: analyze experiments, categorize PRs, bucket experiments, summarize what's been tried, understand experiment history, review merged vs closed results, or asks "what experiments have we run / worked / failed". Also triggers for: "pull the latest experiments", "what's been tried so far", "category breakdown of PRs", "which experiments succeeded", "noam track analysis". When a branch name is mentioned (e.g. "noam branch", "on the noam branch"), pass it as the base branch to scope the fetch to just those PRs.

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

Search and browse Cline session history. Use when the user asks to find, list, inspect, or export Cline sessions by time period, prompt content, status, model, provider, source, mode, workspace, or other criteria. Also use when the user wants to read a session transcript or export sessions to a directory. Trigger phrases include "find my session", "search my session history", "show me past sessions", "what was that session where", "find the session that started with", and any mention of past Cline conversations.

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

可选项驱动的互动小说创作完整规范：支持穿越/自创/创世/随机开局，内置视角一致性、字数区间、选项机制、存档系统与角色卡体系。当用户想玩、想写互动小说，或说「加载小说包」「开个互动小说」「选项小说」「互动故事」时使用。

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

Design and evaluate context compression strategies for long-running agent sessions. Use when agents exhaust memory, need to summarize conversation history, or when optimizing tokens-per-task rather than tokens-per-request.

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

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".

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

Provision a zero-config, no-signup, temporary Upstash Redis database for an AI agent with a single POST to https://upstash.com/start-redis, with no account, API key, or SDK setup required. Use when an agent needs scratch Redis right now and the user has not provided credentials, for short-term memory across tool calls, conversation history, a sub-agent work queue, ranked recall, or a quick prototype or demo. Covers idempotent creation and re-fetching credentials, calling the database through the body-style REST API or the official SDKs, and telling the user how to claim it. The database lives 3 days unless the user claims it; not for production data, PII, or secrets.

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