Automate Reply tasks via Rube MCP (Composio). Always search tools first for current schemas. — from general/automation
Drafts an appellant's Reply Brief that rebuts the appellee's response and reinforces the case for reversal.
「返信案を考えて」「下書き作って」「これに返信したい」「Gmail への返信下書き」「この Gmail に返信」と頼まれたら、opshub MCP の propose.generate (reply_to_source_id 指定) で返信下書きを生成し、ユーザー確認後に propose.apply で保存する。Phase 14 で Gmail…
Use when an agent must never end its turn while an inbound chat message is still unanswered — a Stop hook that blocks turn-end until a reply is sent.
Classifies and automates responses to cold email replies using an 8-category taxonomy, auto-reply playbooks, and human escalation rules.
Draft email replies that match the sender's register — formality, length, directness, and emoji-tolerance read from their message, so the reply lands as native instead of off-key.
Automate Reply IO tasks via Rube MCP (Composio). Always search tools first for current schemas. — from general/automation
Slack スレッドに返信する。「スレッドに返信」「スレッド返信して」「このスレッドに返信」「スレッドで返信」「スレッドに投稿」「スレッドに書き込み」「返信をスレッドで」などで起動。User Token があればユーザーとして返信、なければ Bot として返信。
Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments). The reply addresses all tracked items in one natural-prose message.
Sorts creator replies / emails / automation results into 5 priority buckets, outputs an actionable processing order, and suggests a next step per item (drafting a reply when…
Use when inbound replies to outbound need classification, safe follow-up guidance, and escalation without exposing private notes or inventing buyer intent.
Lightweight entry point for ad-hoc reviewer reply writing: drafting, refining, or editing reply text and manuscript inserts without running the full pipeline.
Reply.io integration. Manage Persons, Organizations, Leads, Activities, Notes, Files and more. Use when the user wants to interact with Reply.io data.
Управление репами в инвентаре: добавить, обновить ветку или удалить субмодуль. Вызывать когда пользователь просит добавить репу, изменить ветку, или убрать субмодуль из проекта.
Repository administration command center -- add and remove collaborators, configure branch protection, manage webhooks, adjust repository settings, audit access, and synchronize…
Minimum standards-adoption surfaces: runtime constitution, project manifest, integrity fences, and conformance entrypoints.
Audit and standardize a repository's agent-readable context, including AGENTS.md, CLAUDE.md, WARP.md, CONTRIBUTING.md, .agents/skills, and specs/ PRODUCT.md and TECH.md contracts.
Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.
Three-stage content quality workflow pattern (Maker creates, Checker validates, Fixer remediates) with detailed execution workflows.
Universal classification system for checker and fixer agents using orthogonal criticality (CRITICAL/HIGH/MEDIUM/LOW importance) and confidence (HIGH/MEDIUM/FALSE_POSITIVE…
Use this when: audit this repo, is this repo ready to release, my README is missing sections, find broken links, check if LICENSE is present, find stale documentation, my docs…
Clones and benchmarks external git repositories against Artibot with quantified 10-dimension scoring, structural comparison, pattern extraction, and adoption recommendations.
Composite skill — configure a fresh or under-configured repo for the release-branch workflow in one pass.
Use when changes touch a skills repository, plugin layout, marketplace integration, repository boundaries, installable skill packaging, or files that may belong in a separate…
Explain Clawdia's repository structure, locate functionality, trace agent/skill wiring, and diagnose config issues.
Use when operations span multiple FrankX ecosystem repositories — bridges Starlight understanding, references, and coordination across ACOS, Arcanea, AI-Ops, and other connected…
Analyzes repository modules for current capabilities, groups them by domain, and identifies strategic gaps against mission objectives
Map the relevant codepath, boundaries, and affected files for a maintenance task before implementation begins.
Map unfamiliar repositories and identify the correct files, dependency paths, conventions, and verification commands before implementation.
Systematic cleanup of repository clutter including build artifacts, duplicates, temp files, and consolidation of scattered directories.
Provides dynamic repository configuration patterns for gh-workflow agents. Use when an agent needs the default branch name for diffs, the repository owner/name for API calls, or…
Build/refresh REPO_CONTEXT.md + REVIEW_BRIEF from repo. Triggers—new repo, zip for later chats, grounded brief. Not code w/o these artifacts.
Workflow pattern standards for creating multi-agent orchestrations including YAML frontmatter (name, description, tags, status, agents, parameters), execution phases…
Use when authorized Git mutation must preserve a large task through semantic milestone, targeted fixup, or exceptional checkpoint commits, normalize task-branch history, or…
Multi-device git sync ritual for repos worked on from several machines, sometimes concurrently. Fetches and diffs origin before work starts, reconciles inbound commits from other…
Sync repo docs (AGENTS, README, ADRs, specs, runbooks, doc comments) ↔ code/workflow. Triggers—big change, drift, docs-align/AGENTS prompts, plan, governance.
Rules and guidelines for evaluating whether a GitHub repository is high-quality and suitable for a video.
Explains any GitHub repository in plain English. Use when asked to explain, understand, analyze, or decode any codebase or GitHub repository.
Use before any implementation to understand the codebase structure, existing patterns, dependency graph, and project conventions.
Use when deploying or updating a homelab self-hosted service through a git-tracked staging repo first, then previewing and applying config into runtime paths like /opt,…
Git Flow ワークフローで開発からdevelopへのマージまでを実行。 「フィーチャーブランチ作って」「PR出して」「コードレビューして」「マージして」などのリクエスト時に使用。 開発中の差分がある状態からブランチを作成します。 develop → main のリリースフローもサポート。 ※ develop → main のマージは人間が実行します。
Guidelines for generating validation/audit reports with UUID chains, progressive writing, and UTC+7 timestamps
Run once after installing the kit to ground .claude/ in this repo — fill placeholders and update references. Edits only .claude/. User-invoked only.
Canonical rule owner for repo-harness ChatGPT integration -- Oracle-first browser/GPT Pro consult and continuation, MCP Connector setup, MCP bridge planning handoff, and Connector…
Checks deploy and private operations configuration for an repo-harness harness without publishing or deploying.
The standard for keeping a project's GitHub repository created, current, organized, and useful at all times.
专门用于深度分析和解读本地或 GitHub 源代码仓库的 Agent Skill。在 Claude Code 中全自动运行，包含质量 Review、迭代优化闭环、并行处理和 subAgent 支持。当用户说"帮我分析这个 GitHub 仓库"或"分析当前目录的代码"时，使用此技能。
Narrow helper skill for README-first AI repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented…
{{ 𝛀𝛀𝛀 }} Provide a detailed high-level overview of this codebase
Triage bugs, enhancements, and backlog items through a small state machine that works with or without a formal issue tracker.
既存GitHubリポジトリのメンテナンス（リリース、変更履歴、Issue等）。ghコマンド使用。 トリガー例: 「リリースノート」「リリース」「issue」「repo-maintain」 ※ PR 作成・マージは repo-flow スキルを使用
Championship-grade repository maintenance. Audits for test artifacts, dependency issues, CI/CD health, documentation sync, and FAF alignment. Generates prioritized cleanup plans.
Gerenciamento padronizado de repositorios GitHub — issues, milestones, pull requests, labels, branch protection e templates.
Single source of truth for repository structure and entry points, including key directories, domain boundaries, shared code, integrations, and build/deploy references
Use when user asks to \"create repo map\", \"generate repo map\", \"update repo map\", \"repo map status\", or \"map symbols/imports\".
Гейт создания любого нового репозитория IWE (экосистемного или личного пространства). Проводит запрос через: классификацию намерения (Pack / SpacePlan / именованный проект /…
Inspects and migrates existing repositories into the agent workflow by inventorying agent instructions, docs, and issue-tracker signals before proposing changes.
Use on first Fusebase Flow install, opening an unfamiliar repo, or after major restructuring; produces durable context map (commands, structure, protected paths, risky…
Onboard new repositories into a managed ecosystem with seed.yaml contracts, CI/CD setup, documentation standards, and governance integration.
Onboard any repository into a standardized Copilot + CI governance baseline. Use for new repos and first-time sessions to ensure immediate standards adoption.