296 件 ・ 関連度順
概要と使いどころ
Analyze budget-versus-actual or forecast-versus-actual performance and turn finance data into a management-ready narrative using variance logic, drivers, cash impact, and forward actions. Use when finance, FP&A, or business leaders need commentary, management accounts, or performance explanation. Do not use for bookkeeping entries, tax filing preparation, or legal accounting sign-off.
日本語の概要は準備中です。原文の説明を表示しています。
Use when turning an article, talk script, lesson, product demo, or narrated explanation into a recordable 16:9 web presentation with step-driven scenes, optional narration alignment, theme tokens, and screen-recording guidance; Chinese triggers include web video, dynamic demonstration, spoken script to video, screen-recordable demonstration, 16:9 demonstration.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a detective/criminal investigator — developing and stress-testing a case theory against alternate explanations, reconciling conflicting timestamps (DVR, cell tower, witness-reported) into a defensible timeline, structuring a suspect/witness interview using a non-accusatorial method, drafting a probable-cause affidavit, or evaluating whether a confession or eyewitness identification is being treated with the right level of certainty.
日本語の概要は準備中です。原文の説明を表示しています。
Explains complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Use when user asks to explain code, understand algorithms, analyze design patterns, wants code walkthroughs, or mentions "explain this code", "how does this work", "code breakdown", or "understand this function".
日本語の概要は準備中です。原文の説明を表示しています。
Audit, classify, validate, and scaffold documentation using the Diataxis framework (Tutorials, How-to guides, Reference, Explanation). Use when user mentions "diataxis", "documentation framework", "quadrant", "doc audit", "doc coverage", "collapsed document", "tutorial vs how-to", "quadrant purity", "documentation types", or wants to classify docs by type.
日本語の概要は準備中です。原文の説明を表示しています。
Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and evidence-backed explanations. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles per locale. Flags machine-translation artifacts for review. Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation after translation completes. Use when user says "translate blog", "blog translate", "uebersetzen", "traduire", "traducir", "translate post", "blog auf Deutsch", "blog en espanol".
日本語の概要は準備中です。原文の説明を表示しています。
Write new blog articles from scratch optimized for Google rankings and AI citations. Generates full articles with template selection, answer-first formatting, Key Takeaways summary box, information gain markers, evidence-backed explanations, sourced statistics, Pixabay/Unsplash images, built-in SVG chart generation, optional FAQ sections, internal linking zones, and proper heading hierarchy. Supports MDX, markdown, and HTML output. Use when user says "write blog", "new blog post", "create article", "write about", "draft blog", "generate blog post".
日本語の概要は準備中です。原文の説明を表示しています。
AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together. Use whenever the user wants their content to rank or be cited in ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com, Google AI Overviews, or Google AI Mode. AI citation optimization audit scoring blog posts for major answer surfaces. Evaluates evidence-backed citability, purpose clarity, entity clarity, structured data, and AI crawler accessibility. Suggests evidence-backed explanations and a 0-100 AI Citation Readiness score. Use when user says "geo", "ai citation", "ai optimization", "citation audit", "aeo", "perplexity optimization", "chatgpt citation".
日本語の概要は準備中です。原文の説明を表示しています。
Detects permission requests triggered at app launch or before meaningful user interaction, which violates Guideline 5.1.1(ii) requiring permissions to be requested only at the moment of need with contextual explanation.
日本語の概要は準備中です。原文の説明を表示しています。
Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For SKMTC docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.
日本語の概要は準備中です。原文の説明を表示しています。
Write, rewrite, review, and organize developer-facing documentation for web software projects. Use when creating or improving README files, docs homepages, quickstarts, tutorials, how-to guides, API/reference pages, conceptual explanations, migration guides, or troubleshooting content for frontend, backend, full-stack, SDK, API, or framework-based web products. This skill applies strong information architecture, task-first page structure, clear voice, runnable examples, version and prerequisite hygiene, accessibility rules, and docs-as-code maintenance habits. Do not use it for marketing copy, legal text, or non-technical customer-support articles.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
日本語の概要は準備中です。原文の説明を表示しています。
Generate visual artifacts: explanations, diagrams, slides, diff views. NOT plan-as-HTML (mk:visual-plan), live media gen (mk:multimodal), or browser QA (mk:qa).
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for adding or updating educational algorithm guides, ensuring consistent patterns and simple explanations suitable for an 8-year-old.
日本語の概要は準備中です。原文の説明を表示しています。
An infographic skill for AI agents — works inside Claude Code, Codex, Hermes, OpenClaw, Cursor, and any agent host that loads skills. Create professional infographics as self-contained HTML files with PNG exports. Use when the user asks to create, design, generate, build, or make an infographic, data visualization, visual explainer, chart poster, cheatsheet, or pocket guide. Trigger phrases include "make this visual", "turn this into a graphic", "visualize this data", "infographic for X", "cheatsheet for X", or when the user provides structured data (tokenomics allocations, ecosystem/partner lists, timelines, comparisons, step-by-step processes) AND asks for a visual output. Covers tokenomics, ecosystem overviews, game overviews, cheatsheets, airdrop guides, comparisons, and process flows. Do NOT trigger for plain text answers, markdown tables, bulleted summaries, questions asking for advice or explanations about a topic (even when the topic is tokenomics, ecosystem, vesting, etc.), inline chat diagrams, or data processing with no visual output requested. The signal is "asks for a visual", not "mentions a keyword".
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose an uncertain bug by designing experiments that distinguish competing causes, especially speculative cache, timing, environment, or concurrency explanations.
日本語の概要は準備中です。原文の説明を表示しています。
Structure persuasive speeches and formal arguments in forensic, legal, policy, and competitive debate styles. Use when the user needs to prepare talks, opening or closing arguments, policy pitches, public explanations, debate speeches, or mentions 'forensic speech', 'formal argument', 'persuasive speech structure', 'debate speech', 'opening statement', 'closing argument'. Turns structured claims into audience-tuned persuasive delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Introduce people to AI, agentic AI, and AI skills with appropriate pedagogy for any audience. Covers LLM analogies, progressive complexity paths, aha-moment demos, audience-tailored explanations, workshop design, and overcoming emotional barriers to AI adoption. Activate on 'explain AI', 'introduce AI', 'AI workshop', 'AI demo', 'teach AI', 'AI literacy', 'onboard to AI', 'AI evangelism', 'explain agentic', 'explain skills to', 'AI training session', 'AI onboarding'. NOT for teaching ML engineering (use ai-engineer), not for building AI features (use ai-engineer), not for prompt engineering (use prompt-engineer), not for building training data pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.
日本語の概要は準備中です。原文の説明を表示しています。
Separates signal from noise in metrics you cannot observe directly, updating a belief from evidence instead of reacting to the latest reading - Bayesian updates over competing explanations, and a filter that says whether this week's move is real. Use when a metric moves and someone wants to act, when diagnosing why traffic or revenue changed, when a dashboard number contradicts intuition, or when deciding whether a trend is real yet.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve repository documentation authority, repair reading paths and explanations, or shape a bounded public projection. Maintain docs after a bounded change when indirect reader promises, generated or paired sources, version/evidence boundaries, or unclear authority need attention. Ordinary known updates stay in normal development; not for isolated prose polishing, code review, or broad runtime audits.
日本語の概要は準備中です。原文の説明を表示しています。
Use for every progress update, status report, problem explanation, ETA, review, acceptance, or completion report to the operator/owner, especially when they ask “到哪了”, “什么问题”, “做了什么”, “结果呢”, “还要多久”, or “说人话”. Translate technical evidence into visible or operational outcomes before details.
日本語の概要は準備中です。原文の説明を表示しています。
Create or edit Canvas Notebook .excalidraw files for diagrams, flows, sketches, architecture maps, and visual explanations. Use when the user asks for an Excalidraw drawing, diagram, board, sketch, canvas, flowchart, architecture diagram, or when a file ending in .excalidraw should be generated. Output only the .excalidraw file unless the user explicitly asks for another artifact.
日本語の概要は準備中です。原文の説明を表示しています。