1,348 件 ・ 関連度順
概要と使いどころ
Convert markdown into a self-contained HTML slide deck with layouts, speaker notes, keyboard navigation, and a content-density linter. Use when building a deck from markdown, cutting an overloaded deck, or timing a talk.
日本語の概要は準備中です。原文の説明を表示しています。
Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.
日本語の概要は準備中です。原文の説明を表示しています。
Helps a lawyer build and use a personalized Legal Guidance Vault — a local folder of structured, privilege-marked entries capturing legal guidance they've given, searchable later by topic, person, or product. Use this skill when the user says "set up my vault," "archive this meeting/email/thread/doc," "log the guidance I gave on [topic]," "save my notes from [meeting]," "what did I say about [topic]," "find the time I advised [person] on [topic]," or "search my vault for [topic]." Runs a setup interview to learn the user's tool stack (meeting notes, calendar, email, docs, messaging, vault location), then generates a customized vault prompt they can reuse in any future Claude session to start archiving and retrieving guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous multi-pass editor for law review articles, student notes, seminar papers and other legal scholarship. Runs six specialized passes — structure, substantive critique, Bluebook citations, grammar and clarity, fact-checking against sources, and a synthesizing memo — and delivers an editorial memo with issues prioritized as critical, substantial or minor and keyed to specific footnotes and paragraphs. Handles articles of any length, including 50,000-word pieces, by chunking on section boundaries. Reads .docx directly. Use when editing, critiquing, workshopping or pre-submission-reviewing academic legal writing. Triggers on "edit my article," "review this draft," "critique my note," "check my Bluebook citations," "is my argument sound," "read my law review piece," "workshop this paper," "pre-submission review." Chunking needs Python 3; fact-checking needs web search; both degrade gracefully without.
日本語の概要は準備中です。原文の説明を表示しています。
When you want to capture into, compile, query, lint, or connect your personal Second Brain. Wraps the Karpathy LLM Wiki schema (Obsidian or any markdown vault) — raw/ (unprocessed sources), wiki/ (AI-compiled interlinked topic pages), outputs/ (generated artifacts). Tool-agnostic in design but defaults to a vault at ${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}/. Six modes — capture (drop something into raw/), compile (process unprocessed raw files into wiki pages, update INDEX.md), query (answer a question from the wiki, save to outputs/), lint (orphans / contradictions / stale / unprocessed raw / topic gaps), connect (suggest new wikilinks between pages), search (quick lookup). Triggers on "/second-brain," "/sb," "capture this," "save this to my brain," "compile the wiki," "process raw notes," "query my wiki," "ask my brain," "lint the wiki," "find connections," "search my notes." Complements deep-research (external corpus) — this is the internal corpus.
日本語の概要は準備中です。原文の説明を表示しています。
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language. Use when the user asks to generate a changelog, write release notes, summarize recent commits, prepare CHANGELOG.md, or document what changed between versions.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records. Supports init (backfill from memory), update (append new entries), and release (summarize for a version).
日本語の概要は準備中です。原文の説明を表示しています。
Generate user-facing release notes for the App Store and Google Play from git history (App Store <=4000 chars, Google Play <=500). Use when generating release notes, app store changelog, play store release, or "what's new" text for a mobile app.
日本語の概要は準備中です。原文の説明を表示しています。
Extract structured data from clinical notes with span-level provenance and null-safety. Use when users say "extract [variables] from this note", "abstract this chart", "pull structured data from these notes", "what does this note say about [field]", or when building a chart-abstraction, registry, or cohort dataset from unstructured clinical text.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize, organize, and normalize messy research materials into an IEEE-ready writing brief before manuscript drafting. Use when Codex needs to process a folder or collection of experiment logs, code files, AI chat exports, idea notes, literature summaries, related-work notes, copied introduction excerpts, Zotero-derived paper summaries, tables, figures, or scattered Markdown/text records and convert them into structured inputs for ieee-writing, ieee-experiment, ieee-citation, ieee-reviewer, or ieee-response.
日本語の概要は準備中です。原文の説明を表示しています。
Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Manages digital garden notes, link structures, and health metrics. Use when curating a knowledge base, pruning stale notes, or tracking content maturity.
日本語の概要は準備中です。原文の説明を表示しています。
Writes and restructures technical documentation - READMEs, tutorials, how-to guides, user guides, architecture docs, onboarding guides, runbooks and SOPs, troubleshooting guides, release notes, and knowledge base articles - grounded in the actual code or product, with commands and examples verified where possible. Use when the user asks to document a project, feature, system, or process, write or fix a README, explain a codebase to new developers, turn notes into a guide, or make existing docs clearer. For endpoint-by-endpoint API reference or OpenAPI specs, use api-documentation-writer; for CLAUDE.md or AGENTS.md files, use claude-md-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Use when turning a folder of research PDFs into Obsidian notes, even if Obsidian is not named. Writes one templated literature note per paper and extracts cross-linked atomic concept notes, never overwriting existing ones. A .bib or Zotero library is /lit-sync.
日本語の概要は準備中です。原文の説明を表示しています。
Use when references in a .bib file (often from /search-lit) should land in Zotero and Obsidian. Syncs them to the Zotero library, writes Obsidian literature notes and extracts cross-cutting concept notes once enough accumulate. A folder of PDFs is /obsidian-paper-vault.
日本語の概要は準備中です。原文の説明を表示しています。
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "make an audiobook", "narration script", "narrator", "ACX", "Findaway", "pronunciation guide", "how long is the audiobook", "adapt to a screenplay", "Fountain", "screenplay", "picture book", "spreads", "illustration notes", "art notes", "comic script", "comics script", "graphic novel", "panels", "interactive edition", "turn the book into Ink or Twine", "translate the book", "translation", "foreign edition", "glossary for translators", or wants to turn a story project into another form or language, or to plan a picture book. NOT for writing a new branching or choose-your-own-adventure story (use interactive-fiction), or writing rhyming picture-book text (use verse-craft).
日本語の概要は準備中です。原文の説明を表示しています。
Interact with Xiaohongshu (小红书, RED, Little Red Book) — search notes, read note details, view comments, browse user profiles and posts, get home feed. Use this skill whenever the user mentions Xiaohongshu, 小红书, RED, RedNote, Little Red Book, wants to search for lifestyle/beauty/travel content, read XHS discussions, look up XHS users, or browse trending notes. Also trigger when the user pastes a xiaohongshu.com URL (e.g. xiaohongshu.com/explore/noteid) or mentions an XHS note ID.
日本語の概要は準備中です。原文の説明を表示しています。
Process YouTube videos into summarized Obsidian notes. Use when given a YouTube URL to summarize, extract insights, or turn videos into notes. Triggers on "summarize this video", "process this YouTube", "what's this video about", or any YouTube URL shared for processing.
日本語の概要は準備中です。原文の説明を表示しています。
把课堂视频（本地或 B 站/YouTube）、文字稿、课件三者（任意组合）整理成一份详细的中文 Markdown 课堂笔记，输出按课程标题命名的 `{title_name}.md`（首行为 `# 文档标题`）+ 相对路径图片。Markdown 工作流，与上游 `lecture-to-notes` 的 LaTeX/PDF 输出并行存在；上游 skill 完全不动。触发词：markdown 笔记、md 笔记、视频转 markdown、Markdown 讲义、不要 LaTeX、不要 PDF、纯文本笔记。
日本語の概要は準備中です。原文の説明を表示しています。
Convert meeting notes into owners, action items, decisions, and follow-up messages.
日本語の概要は準備中です。原文の説明を表示しています。
Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops. Triggers on requests to set up a changelog system, publish releases, or when user asks "how should we publish releases?", "changelog as marketing", "release notes", "Stripe-style changelog", "what to do with our release notes", "ship and tell". Outputs MON-CHG-* changelog entries and per-channel formats.
日本語の概要は準備中です。原文の説明を表示しています。
Cut a new TMDb release — work out the next SemVer version from the evidence, do the pre-tag housekeeping a tag would otherwise freeze in place, draft release notes, then tag and publish the GitHub release. Presents the version (with its reasoning) and the full notes for approval and STOPS; nothing is tagged or published until you say go.
日本語の概要は準備中です。原文の説明を表示しています。