Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
日本語の概要は準備中です。原文の説明を表示しています。
OneWave-AI/claude-skills3392026年10月2日 更新
無料GitHub で公開
gmail-to-crm-pipeline
Uses MCP Connectors to read Gmail inbound leads, score them by ICP fit, draft personalized responses, and log qualified leads to your CRM. Turns your inbox into an automated pipeline.
含まれるファイル（8）
- SKILL.md3.2 KB
- references/configuration.md3.3 KB
- references/crm-schema.md6.9 KB
- references/gmail-retrieval.md3.2 KB
- references/lead-extraction.md3.0 KB
- references/pipeline-report.md3.7 KB
- references/response-templates.md4.2 KB
- references/scoring-model.md4.7 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Gmail-to-CRM Pipeline
Turn a Gmail inbox into a structured sales pipeline using Claude's MCP Connectors -- the Gmail connector reads and drafts email, and the Supabase connector persists CRM data. No external scripts or API keys required.
Workflow
- Connect. Verify the Gmail and Supabase MCP Connectors are available. On first run, create the CRM tables and seed config. Load ICP config from the
pipeline_configtable. Seereferences/configuration.md(first run, error handling) andreferences/crm-schema.md. - Search. Run the targeted Gmail search queries to find unread lead emails over the time window (default: last 24 hours). Collect unique message IDs and deduplicate. See
references/gmail-retrieval.md. - Parse. Read each unique message, strip signatures and disclaimers, and extract the structured field set. See
references/gmail-retrieval.md. - Extract. Build the lead profile (contact, company, inquiry, metadata) for each email. Set missing fields to
nullrather than guessing. Seereferences/lead-extraction.md. - Score. Score each lead on ICP fit (0-40), intent (0-35), and urgency (0-25), then apply adjustment modifiers. Map the total to a qualification tier and priority. See
references/scoring-model.md. - Draft. For each qualified lead (score >= 25), draft a personalized, tier-appropriate response and save it as a Gmail draft. Never auto-send. See
references/response-templates.md. - Log. Check for duplicates, then insert or update the lead in Supabase, log activity, and set the next action by priority. See
references/crm-schema.md. - Report. Query the pipeline snapshot and generate
lead-pipeline-report.mdin the working directory, then display the executive summary. Seereferences/pipeline-report.md.
Between runs, handle manual lead commands (mark contacted, move stage, disqualify, add note, schedule follow-up, query leads) and ICP/search customization. See references/configuration.md.
Hard Rules
- Never auto-send email -- always create drafts for the user to review and send.
- Never store raw email bodies or credentials in Supabase or any report; store structured data and key quotes only.
- Treat all lead and email content as confidential.
Contents
references/gmail-retrieval.md-- Gmail MCP tools, search queries, parsing rules, extracted field set.references/lead-extraction.md-- Lead profile JSON schema and extraction guidelines.references/scoring-model.md-- ICP, intent, urgency scoring tables; tier mapping; adjustment rules.references/response-templates.md-- Per-tier response templates, personalization rules, anti-patterns, draft creation.references/crm-schema.md-- Supabase MCP tools, table DDL, logging procedure and SQL.references/pipeline-report.md-- Report Markdown structure and reporting SQL queries.references/configuration.md-- First-run setup, customization, manual commands, error handling, privacy, invocation triggers.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
日本語の概要は準備中です。原文の説明を表示しています。
OneWave-AI/claude-skills3392026年10月2日 更新
Use to test whether an AI agent, prompt, or skill actually works before or after it ships — build a small eval set, score runs, and catch regressions when the prompt or model changes. Trigger when the user asks whether a prompt is good, wants to compare models or versions, sees inconsistent agent output, or is about to put an agent in front of customers.
日本語の概要は準備中です。原文の説明を表示しています。
OneWave-AI/claude-skills3392026年10月2日 更新
Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
日本語の概要は準備中です。原文の説明を表示しています。
OneWave-AI/claude-skills3392026年10月2日 更新
Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
日本語の概要は準備中です。原文の説明を表示しています。
OneWave-AI/claude-skills3392026年10月2日 更新
Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
日本語の概要は準備中です。原文の説明を表示しています。
OneWave-AI/claude-skills3392026年10月2日 更新