1,887 件 ・ 関連度順
概要と使いどころ
Suede-owned earned-media discipline. Use when building a media list, validating a story angle, drafting a journalist pitch, preparing a press kit, evaluating newsjacking, or answering a reporter request. NOT FOR: directory submissions (use suede-directory-submissions), launch packaging (use suede-launch-packaging), social publishing (use suede-social), or contacting anyone without approval.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for writing conventional commit messages. Use when committing changes, writing commit messages, or reviewing commit history.
日本語の概要は準備中です。原文の説明を表示しています。
Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive status reports for git repositories. Analyzes commits, codebase structure, type errors, branch health, dependency status, GitHub PRs/issues/CI, working tree changes, and optionally integrates with `td` (task management CLI) if a `.todos` folder is present. **TRIGGERS - Use this skill when:** - User asks for the status of a git project or repo - User asks "what's going on in [project]" or "give me an overview of [repo]" - User wants a project summary, progress report, or codebase overview - User asks about recent commits, code structure, or project health - User says "check my project" or "project status" **Output:** A rich, structured text report covering overview, branches, commit history, codebase breakdown, GitHub activity, dependency health, issues/errors, working tree changes, task management, and summary.
日本語の概要は準備中です。原文の説明を表示しています。
生成短视频脚本和分镜。输入产品/主题描述、目标受众、时长，输出完整脚本+分镜结构（JSON/YAML）。支持多种模板：痛点-解决、反转剧情、before-after。触发词：视频脚本、短视频文案、分镜、storyboard、video script。
日本語の概要は準備中です。原文の説明を表示しています。
Use when reading or writing files in an Obsidian vault that is synced with obsync. Ensures changes are pulled before reading and pushed after writing. Also covers sync status, file history, version restore, and diagnosing sync issues.
日本語の概要は準備中です。原文の説明を表示しています。
Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.
日本語の概要は準備中です。原文の説明を表示しています。
Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints. Use when cto-architect needs to create actionable technical roadmaps from architecture designs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when capturing what a feature must do - write testable user-story requirements that state WHAT and WHY, never HOW, with assumptions made explicit
日本語の概要は準備中です。原文の説明を表示しています。
Persistent memory across AI sessions using ChromaDB vector database. Stores and retrieves context from past conversations, decisions, and code. Use when user asks to remember something, search past conversations, recall what was done before, save context for later, or find information from previous sessions. Do NOT use for git history or file-based notes.
日本語の概要は準備中です。原文の説明を表示しています。
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit changes, make a PR, rebase, squash, clean up branches, or follow a Git workflow. Do NOT use for CI/CD pipeline configuration (use ci-cd), code review (use code-review), or GitHub Actions workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Download GitHub repos as clean source code (no .git history) to WORKDIR. Use when cloning repos for analysis or modification. Not for monorepos.
日本語の概要は準備中です。原文の説明を表示しています。
宣传片逐镜头分镜脚本。根据创意简报生成每个 Shot 的 7 维画面描述和详细 HyperFrames 提示词，是整条视频质量的关键。当用户确认 brief 后自动进入。
日本語の概要は準備中です。原文の説明を表示しています。
宣传片两包素材生产。Pack A 使用当前可用图片生成能力生成产品图、概念图、UI 模拟图或风格补充图；Pack B 使用官网、应用截图、浏览器搜索、GitHub 或开源素材收集真实产品信号。当 storyboard 确认后进入。
日本語の概要は準備中です。原文の説明を表示しています。
产品宣传片制作总控 skill pack。用于从产品说明、官网、应用截图或 GitHub 仓库制作 60-90 秒宣传视频，按阶段完成 brief、storyboard、素材、HyperFrames 剪辑、BGM 设计和交付。当用户要做宣传片、产品视频、项目介绍视频、launch video、开源项目 promo、BGM 卡点或真实软件界面宣传片时使用。
日本語の概要は準備中です。原文の説明を表示しています。
为产品宣传片生成高度贴合画面节奏的 BGM 方案与音乐生成 Prompt。读取 brief、storyboard、EDL、DESIGN 或成片，输出音乐风格、BPM、情绪曲线、卡点表、Mureka/Skywork Music Maker 英文 prompt、负面 prompt 和剪辑建议。当用户要“配乐”“BGM”“背景音乐”“音乐 prompt”“卡点”“按转场做音乐”时触发。
日本語の概要は準備中です。原文の説明を表示しています。
Create, curate, and grow email newsletters across all formats and strategies. Use when working on newsletters, email newsletters, weekly digests, link roundups, curated content, audience building, subscriber engagement, or content distribution. Covers 6 newsletter formats (curated/link roundup, story-driven, educational, interview, data-driven, personal update), editorial issue structure, content sourcing workflows, commentary writing, sending cadence, subject line optimization, subscriber growth, and engagement metrics. Trigger keywords: newsletter curation, curated newsletter, newsletter writing, newsletter format, newsletter strategy, newsletter template, content curation, subscriber growth.
日本語の概要は準備中です。原文の説明を表示しています。
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of implementation work in a repo that signs commits ("коммиты не подписаны", "ssh-keygen висит", "gpg failed to sign"). Loaded by senior-dev, devops.
日本語の概要は準備中です。原文の説明を表示しています。
Read a Hyperliquid account from the desk computer - positions and margin, spot balances, open orders including trigger details, fills, funding paid, ledger updates, order status by oid or cloid, historical orders, portfolio history, fee tier and rate-limit budget - with curl and Python SDK examples. Read-only, needs only the account address. Use for sizing inputs, book checks, reconciliation and reviews.
日本語の概要は準備中です。原文の説明を表示しています。
How the Strategist works with the user to turn their own trading idea into explicit rules, backtest it honestly on Hyperliquid candle and funding history, and paper-trade it on testnet through the desk lifecycle. Method only - the desk ships no strategies and makes no return claims. Use when the user wants to design, test, compare or paper-trade an idea.
日本語の概要は準備中です。原文の説明を表示しています。
汽车TVC、品牌片、汽车文案剧本、车辆资产与图片/视频提示词、分镜及Blender白模运镜。按人物叙事、生活观察、产品演示、造型光影等意图选择方法，维护车型身份与驾驶安全带连续性；不处理购车行情或维修问答。
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agent needs Dreamina（即梦） login, sessions, task history, Seedream 5.0 Pro, or Seedance 2.5 image/video generation through the dreamina CLI.
日本語の概要は準備中です。原文の説明を表示しています。
A dated chronology of one topic across the user's recorded coding-agent sessions — the lessons the graph learned about it and the prompts that named it, oldest first. Use only when the user explicitly asks for the history or timeline of a topic across their sessions ("how did X evolve", "when did we first discuss X") or asks for the `cognee-timeline` skill by name. Not for questions about code or the current task.
日本語の概要は準備中です。原文の説明を表示しています。
A dated chronology of one topic across the user's recorded coding-agent sessions — the lessons the graph learned about it and the prompts that named it, oldest first. Use only when the user explicitly asks for the history or timeline of a topic across their sessions ("how did X evolve", "when did we first discuss X") or invokes /cognee-timeline. Not for questions about code or the current task.
日本語の概要は準備中です。原文の説明を表示しています。