303 件 ・ 関連度順
概要と使いどころ
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
日本語の概要は準備中です。原文の説明を表示しています。
Aggregate parallel agent results into concise output
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a short executive summary for the current rolling-wave project. Use when the user wants a concise status update, investor/team-friendly summary, leadership summary, project progress snapshot, or TL;DR of completed slices, the current slice plan, and upcoming slices.
日本語の概要は準備中です。原文の説明を表示しています。
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
日本語の概要は準備中です。原文の説明を表示しています。
Read the project's knowledge record before answering from memory or from the files. Use before answering about the project's state, a number, a date, a decision, a source, a deadline or what was agreed - even a casual 'what's the situation with X' or 'is that quote still current'; before changing a recorded value; and whenever the opener or a grounding line names entries. After finding relevant IDs, prefer kpop context to read them with their declared dependencies and checks. Uses pull for concise readings or when the checked reader is unavailable, affects for changed inputs, and search when no ID is known. A missing id is not absence. Not for showing the record's page (the hub skill). Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesise a status, standup, or situation-report from current work state. Trigger when a team member needs a concise summary of where things stand, what is blocked, and what is next.
日本語の概要は準備中です。原文の説明を表示しています。
Converts structured prospect research into concise outreach preparation briefs. Use when the user provides prospect or account research and wants a brief with context, angles, and claims to verify. It generates a research brief and must not invent personalization or send outreach.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when a user asks to polish, rewrite, humanize, de-AI, localize, or oralize Chinese writing, including short-video scripts, articles, social posts, speeches, newsletters, and personal-IP content. The skill diagnoses “AI味”, preserves the user's meaning, adapts to optional style samples, replaces translation-like phrasing with natural Chinese expression, and outputs a polished version plus concise revision notes.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user asks for a concise Solana token research snapshot with market, trade, and security context
日本語の概要は準備中です。原文の説明を表示しています。
Periodic repository health check — install, full validation, unused-code scan, outdated/vulnerable dependencies, and docs drift — ending in a concise report and, when there are safe fixes, a single PR. Designed to run unattended from a scheduled routine; also usable on demand.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user explicitly invokes the `if` skill or asks for a concise, laconic, no-fluff, or to-the-point answer. Do not trigger on the ordinary word or programming keyword `if`. Detailed, step-by-step, exhaustive, educational, or fixed-length requests activate only when they also include an explicit invocation or brevity request.
日本語の概要は準備中です。原文の説明を表示しています。
Create concise checklist cheatsheets from official tool docs. Use for docs URLs, setup guides, or updating existing cheatsheets. Don't use for long tutorials or API references.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically explore an unfamiliar codebase and build a reusable architecture summary. Use for repo onboarding, understanding legacy or inherited code, mapping architecture before a migration or refactor, tracing a bug or feature path, or answering "what does this project do?". Documentation-first, then data flow — ends in a concise technical architecture summary with file:line evidence, not a raw file dump.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Steven's Bash script style rules: strict mode, minimal validation, concise logic, executable scripts, and no unnecessary comments or echoes. Use when creating, reviewing, or refactoring shell scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Keep decision maps as concise routers from decisions to canonical documents and validation guardrails.
日本語の概要は準備中です。原文の説明を表示しています。
Review someone else's PR through an architectural/strategic lens — does it shift design, raise complexity, or quietly change precedent? Drives a brief reflective discussion with the user, then posts a concise review comment via `gh`. Defers line-level and bug-hunting concerns to AI review bots and the PR author.
日本語の概要は準備中です。原文の説明を表示しています。
Turns one meeting transcript, recording recap or set of raw notes into concise DRAFT minutes returned in the chat as a single Markdown document: header metadata, attendance and apologies, agenda items each with a short neutral summary and outcome, numbered decisions with an owner, numbered action items with owner and due date, open questions, carried-over actions and the next-meeting line, every entry backed by a short verbatim source fragment and every missing fact marked UNKNOWN. Use when the user asks to "write the minutes", "draft minutes from this transcript", "turn these notes into meeting minutes", "produce the minutes of meeting for today's call", "tidy my rough minutes into the standard format" or "prepare the minutes for circulation". Do not use for extracting action items, task lists or per-owner follow-up emails alone, use transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Recast a supplied everyday photo as a witty illustrated product instruction sheet with a large Chinese title and concise English annotations. Use for 日常说明书、宠物使用说明、生活物品冷幽默说明图 or a fictional everyday object manual poster.
日本語の概要は準備中です。原文の説明を表示しています。
Capture decisions and commitments after a meeting and draft a concise follow-up.
日本語の概要は準備中です。原文の説明を表示しています。
Extract bounded, source-linked context from large files or many inputs. Use when context is too large, files are oversized, or a task needs concise excerpts.
日本語の概要は準備中です。原文の説明を表示しています。
Write B2B cold outreach and follow-up sequences grounded in relevance, evidence, concise value, compliant sending practices and clear calls to action.
日本語の概要は準備中です。原文の説明を表示しています。