本文へ移動
cccskills

仕事効率化のスキル

メール、カレンダー、タスク管理、自動化(7,815 件)

価格や並び順で絞り込む

Suede AI B2B cold-email discipline: evidence-based personalization with a named source for every opening line, 2-to-4-word subject lines, bodies under 75 words, one low-friction ask, bounded 3-to-5-touch follow-up sequences, and a deliverability gate built on current Gmail, Yahoo, Microsoft, and CAN-SPAM rules. Use when writing or repairing outbound email to qualified prospects. NOT FOR: building or qualifying the prospect list (use suede-prospecting), lifecycle or nurture email to opted-in contacts (use suede-emails), or broader sales collateral (use suede-sales-enablement).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1252026年10月24日 更新

Suede AI artist campaign rollout for a song, release, era, show, or catalog moment. Use when an artist needs a complete campaign across surfaces (identity, era world, hooks, release stunts, fan rituals, visualizers, merch, setlists, catalog revival, collaborator outreach) or the full announce, tease, release-week, and post-drop package with calendar, email, site copy, search-ready release page, and fan actions. Picks one of twelve lanes or stitches them together, and flags rights gaps instead of resolving them. NOT FOR: single-surface conversion copy (use suede-copy); sync licensing packaging (use suede-sync-packaging); rights gaps or a rights package (use suede-rights-passport); software, repo, or skill-pack releases (use suede-launch-packaging).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1252026年10月24日 更新

Suede AI agent-team orchestrator, the method behind multi-agent automation: split complex work into coordinated lanes with explicit file ownership, WIP collision detection, quality gates, escalation thresholds, rollback plans, and handoffs that prove what shipped. Use when one shared change needs safe parallel ownership across builders and reviewers, when a lane map must be resolved before anyone opens a file, or when running a repeatable public-repository contribution program with issue scoring, atomic task leases, isolated worktrees, and explicit publication authority. NOT FOR: one repo change a bundled DAG can run end to end (use suede-graph-flo-xr); reviewing or grading a diff (use suede-code); CI, branch protection, or merge-gate wiring (use suede-ci-gate); picking which single skill fits a request (use suede-workflow-skills).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1252026年10月24日 更新

Suede AI lifecycle email design for welcome, onboarding, nurture, re-engagement, post-purchase, and trigger-based sequences, with entry criteria, cadence, message roles, exact copy, deliverability checks against current Gmail, Yahoo, and Microsoft sender rules, and a measurement plan. Use when the user needs a multi-email flow: drip campaigns, welcome series, win-back flows, or trigger-based automations. NOT FOR: cold prospecting (use suede-cold-email), SMS in the same lifecycle program (use suede-sms), in-product activation flows (use suede-onboarding), or lifecycle-stage operations beyond email (use suede-revops).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1252026年10月24日 更新

Configure AionUi itself with the bundled aioncore CLI. Use when asked to set up or change assistants, assistant rules, skills, MCP servers, model providers, agents, scheduled tasks, or settings.

日本語の概要は準備中です。原文の説明を表示しています。

iOfficeAI/AionCore1232026年10月15日 更新

cron

無料

Scheduled task management - create, query, update scheduled tasks to automatically execute operations at specified times.

日本語の概要は準備中です。原文の説明を表示しています。

iOfficeAI/AionCore1232026年10月15日 更新

Guide for creating effective skills. Use when the user wants to create a new skill or update an existing one to extend Claude with specialized knowledge, workflows, or tool integrations.

日本語の概要は準備中です。原文の説明を表示しています。

iOfficeAI/AionCore1232026年10月15日 更新

aamp

無料

AAMP (Agent-to-Agent Mail Protocol) via aamp-cli. Use this skill when the agent needs to register a mailbox, listen for incoming AAMP mail, inspect a task thread, complete a pairing URL, dispatch a task, or reply with task.result / task.help_needed. Prefer the CLI over hand-written HTTP requests.

日本語の概要は準備中です。原文の説明を表示しています。

larksuite/aamp1232026年7月29日 更新

aamp

無料

AAMP (Agent-to-Agent Mail Protocol) — gives this agent an email identity and lets it exchange structured tasks with other AAMP nodes via email. Use this skill to register an identity, check for incoming tasks, and reply with results or help requests.

日本語の概要は準備中です。原文の説明を表示しています。

larksuite/aamp1232026年7月29日 更新

deepswarm

無料

Use when running parallel AI workers for any long-running or multi-turn batch API task. Auto-calculates optimal workers + stagger. Supports tiered delegation (V4 Pro orchestrator → V4 Flash workers). 99.95% API success rate at scale.

日本語の概要は準備中です。原文の説明を表示しています。

amanning3390/deepswarm1222026年5月5日 更新

Delegate tasks to specialized subagents for parallel or sequential execution.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年10月12日 更新

td

無料

Manage tasks and issues with the td CLI. Use for creating, tracking, querying, and handing off work items. Covers task lifecycle, session management, structured handoffs, epics, dependencies, and boards.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年10月12日 更新

Manage design work in Penpot — create projects, organize pages, build components, export assets, review designs visually, and handle design-to-code handoff. Use when asked to create designs, manage Penpot projects, build components, export tokens, set up a new design project, review a design, take screenshots, or show what something looks like.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年10月12日 更新

Read, create, and update notes in Espen's Obsidian vault (PARA method). Use when asked about notes, tasks, projects, dashboards, daily logs, or anything in the vault.

日本語の概要は準備中です。原文の説明を表示しています。

espennilsen/pi1222026年10月12日 更新

vibe

無料

Delegate a coding task to Mistral Vibe and supervise the result via git diff. Trigger: /vibe <instruction>. Claude orchestrates, Vibe codes. Also handles /vibe-report [--since N] [--project NAME] [--fails] — token/cost/failure report.

日本語の概要は準備中です。原文の説明を表示しています。

pcx-wave/vibe-skill1212026年10月1日 更新

Closed-loop compare-adjust-repeat workflow for fitting Blender models to supplied front/side/back/top templates and originals. Use when the user asks to compare the product to templates/originals and adjust until it fits across all dimensions, or when all views must pass measurable bbox/centroid/silhouette/edge validation before export.

日本語の概要は準備中です。原文の説明を表示しています。

RobLe3/cc-blender-skill1202026年10月13日 更新

Harmonize multiple Blender skills into a coherent pipeline with clear activation precedence, handoff artifacts, dependency gates, and conflict-resolution rules. Use when a Blender task spans several skills, when reference-locked work conflicts with generic production workflow, after adding/updating skills, or when repeated failures indicate skill interference or missing inter/intra-play.

日本語の概要は準備中です。原文の説明を表示しています。

RobLe3/cc-blender-skill1202026年10月13日 更新

End-to-end production workflow guidance for Blender — the order to assemble scenes (block-out → camera → light → forms → materials → detail → render → composite → export), critique protocols, time budgets, and recovery patterns. Use whenever the user asks to "make a complete scene / hero shot / production-quality render", "what's the right order to do this", "set up a full pipeline", or has a multi-step request crossing modeling + lighting + materials + rendering. Make sure to use this skill for any request that spans multiple phases of 3D work, even if the user does not say "workflow" — also covers "make a final image of X", "produce a hero render", "professional-looking result".

日本語の概要は準備中です。原文の説明を表示しています。

RobLe3/cc-blender-skill1202026年10月13日 更新

Use when a task touches a Jupyter or marimo notebook, asks to productionise or schedule notebook logic, or when you are tempted to do the work in a notebook — extract logic into tested modules, keep the notebook thin and reproducible, and commit it the way the repo does

日本語の概要は準備中です。原文の説明を表示しています。

makifbaysal/tasktrooper1182026年10月21日 更新

Use when you start an analiz task - explore every affected repository and resolve unknowns before writing the report

日本語の概要は準備中です。原文の説明を表示しています。

makifbaysal/tasktrooper1182026年10月21日 更新

Use when an approved analiz spans more than one repository - split the work per repository and open one or more tasks per repository, each carrying its own plan slice

日本語の概要は準備中です。原文の説明を表示しています。

makifbaysal/tasktrooper1182026年10月21日 更新

Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analiz_review column

日本語の概要は準備中です。原文の説明を表示しています。

makifbaysal/tasktrooper1182026年10月21日 更新

Use when a task in code_review was sent back before (an earlier need_revision comment exists) - verify every prior point was fixed at its root

日本語の概要は準備中です。原文の説明を表示しています。

makifbaysal/tasktrooper1182026年10月21日 更新

Use when an analiz task arrives in done (approved) - turn the approved split into implementation tasks with repository, AC, derived_from and ordering arguments

日本語の概要は準備中です。原文の説明を表示しています。

makifbaysal/tasktrooper1182026年10月21日 更新