复制安装命令
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
A model-agnostic agent-skills platform.
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
来源文件:README.md
A model-agnostic agent-skills platform. The canonical layer is harness-free by construction; Claude Code is currently the verified-native harness. Other harnesses remain engineering candidates until their native-path integration is verified; source research alone is never presented as public support.
Inside Claude Code, one command installs the whole marketplace:
/plugin marketplace add jeremylongshore/claude-code-plugins
Or use the CLI:
pnpm add -g @intentsolutionsio/ccpi
ccpi install devops-automation-pack
Browse the marketplace · Explore plugins · Download bundles
Killer Skill of the Week — no-ai-slop by Peter Yang
Strip AI slop from any draft — named-pattern edits that keep the writer's real voice
no-ai-slop does two jobs and refuses to fake a third. In Edit mode it makes the minimum effective edit — cutting throat-clearing, weak verbs, and abstract nouns while deliberately preserving the writer's cadence, bluntness, humor, and honest admissions, so a rough draft still sounds like the same person afterward. In Detect mode it names each AI-slop pattern it finds, quotes the offending line, and gives the fix in a few words — and pointedly does NOT score the draft or guess whether an AI wrote it. That restraint is the whole point: AI detectors guess; named patterns are evidence the reader can check. MIT-licensed, single focused skill, actively maintained by Peter Yang.
"AI detectors guess. Named patterns are evidence the user can check." — Peter Yang
Grade: A | Week of July 22, 2026 (W30) | View on GitHub
Previous picks: tonone, mnemos, databricks-pack, kobiton-automate, skyvern, code-cleanup, web-analytics, token-optimizer, executive-assistant-skills, skill-creator, cursor-pack, crypto-portfolio-tracker. See all at tonsofskills.com.
Every number below names the cohort it counts and the command that reproduces it — an unlabeled count is how a corpus ends up with five contradictory answers to "how many skills."
| Count | Cohort | Reproduce with |
|---|---|---|
| 442 | catalog plugins (catalog-entry cohort) | node scripts/generate-readme-toc.mjs over marketplace.extended.json |
| 3,067 | marketplace-visible skills (distinct) | node -e "import('./scripts/corpus-resolver.mjs').then(m=>console.log(m.resolveCorpus('marketplace-visible').length))" |
| 347 | agent definitions in plugins | git ls-files 'plugins/**' | grep '/agents/.*\.md' |
| 19 | plugin categories | ls -d plugins/*/ |
Across 396 published packages in the claude-code-plugins namespace. Updated daily by GitHub Actions.
| Window | All packages | Established (>30d) |
|---|---|---|
| Last 24 hours | 962 | 962 |
| Last 7 days | 2,920 | 2,916 |
| Last 30 days | 12,868 | 12,779 |
"Established" excludes packages first published within the last 30 days, so a bulk-publish event doesn't dominate the headline.
Top 10 by last 30 days:
Last refreshed 2026-08-19T03:03:05.709Z.
Five real questions, five doors — each resolves to a live, generated surface, never a hand-maintained list:
The 19 categories below link into the live marketplace. Plugin counts are the catalog-entry cohort — regenerated from marketplace.extended.json by this generator; the catalog itself lives on tonsofskills.com, never in this file (§ 6A of the platform blueprint).
| Category | Plugins | |
|---|---|---|
| 🤖 | AI & Machine Learning | 36 |
| 🎭 | AI Agents & Agency | 10 |
| 🔌 | API Development | 26 |
| 💼 | Business Tools | 6 |
| 👥 | Community | 21 |
| ₿ | Crypto & Web3 | 27 |
| 💾 | Database | 26 |
| 🎨 | Design | 2 |
| 🔧 | DevOps & Infrastructure | 36 |
| 📚 | Examples & Templates | 5 |
| 🧩 | MCP Servers | 16 |
| 📦 | Packages | 5 |
| ⚡ | Performance | 25 |
| ✅ | Productivity | 30 |
| 🎁 | SaaS Skill Packs | 106 |
| 🔐 | Security | 27 |
| ✨ | Skill Enhancers | 9 |
| 🧪 | Testing | 28 |
| 📁 | Analytics | 1 |
Four artifact classes live in this repository, distinguished on sight and never blurred — provenance is a truth requirement here, not a UX nicety:
| Class | What it is | How the reader can tell |
|---|---|---|
| Canonical skill | First-party, harness-free, the source of truth | No .source.json in its plugin directory |
| Generated adapter | A thin, machine-produced harness projection | Lives under a generated path with a "generated — do not edit" header |
| First-party package | An Intent Solutions distribution (npm, cowork zip) | @intentsolutionsio scope, IS-authored license |
| Upstream mirror | Somebody else's work, hosted mirror-by-default | .source.json present — upstream author, license, and pinned commit recorded |
Not yet certified. The certification program (tiers T0–T4 with retained, hash-matched evidence) is a later epic of the platform blueprint; until its report exists, no artifact on this surface claims a tier. This line is rendered from the absence of certification-report.json — honestly, not cosmetically.
Start with the contribution guide, then the intake and review standards every submission passes through:
External plugins are hosted mirror-by-default: the contributor's repository stays the source of truth, every mirrored source is pinned in a content lockfile, and upstream credit — author, license, resolved commit — is recorded in the mirror itself. Improvements flow by upstreaming to the author's repository, never by silently editing the mirror. The full decision record is the external-sync model.
MIT for the repository scaffolding and first-party tooling; each plugin carries its own license in its manifest, and mirrored plugins keep their upstream license verbatim.
name: apollo-core-workflow-b
description: 'Implement Apollo.io email sequences and outreach workflow.
Use when building automated email campaigns, creating sequences,
or managing outreach through Apollo.
Trigger with phrases like "apollo email sequence", "apollo outreach",
"apollo campaign", "apollo sequences", "apollo automated emails".
'
allowed-tools: Read, Write, Edit, Bash(npm:*), Bash(pip:*), Grep
version: 1.13.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- apollo
- workflow
compatibility: Designed for Claude CodeBuild Apollo.io email sequencing and outreach automation via the REST API. Sequences in Apollo are called "emailer_campaigns" in the API. This covers listing, searching, adding contacts, tracking engagement, and managing sequence lifecycle. All endpoints require a master API key.
apollo-core-workflow-a (lead search)// src/workflows/sequences.ts
import axios from 'axios';
const client = axios.create({
baseURL: 'https://api.apollo.io/api/v1',
headers: { 'Content-Type': 'application/json', 'x-api-key': process.env.APOLLO_API_KEY! },
});
export async function searchSequences(query?: string) {
const { data } = await client.post('/emailer_campaigns/search', {
q_name: query, // optional name filter
page: 1,
per_page: 25,
});
return data.emailer_campaigns.map((seq: any) => ({
id: seq.id,
name: seq.name,
active: seq.active,
numSteps: seq.num_steps ?? seq.emailer_steps?.length ?? 0,
stats: {
totalContacts: seq.unique_scheduled ?? 0,
delivered: seq.unique_delivered ?? 0,
opened: seq.unique_opened ?? 0,
replied: seq.unique_replied ?? 0,
bounced: seq.unique_bounced ?? 0,
},
createdAt: seq.created_at,
}));
}
Before adding contacts to a sequence, you need the email account ID that will send the messages.
export async function getEmailAccounts() {
const { data } = await client.get('/email_accounts');
return data.email_accounts.map((acct: any) => ({
id: acct.id,
email: acct.email,
sendingEnabled: acct.active,
provider: acct.type, // "gmail", "outlook", "smtp"
dailySendLimit: acct.daily_email_limit,
}));
}
The add_contact_ids endpoint enrolls contacts into an existing sequence. You must specify which email account sends the messages.
export async function addContactsToSequence(
sequenceId: string,
contactIds: string[],
emailAccountId: string,
) {
const { data } = await client.post(
`/emailer_campaigns/${sequenceId}/add_contact_ids`,
{
contact_ids: contactIds,
emailer_campaign_id: sequenceId,
send_email_from_email_account_id: emailAccountId,
sequence_active_in_other_campaigns: false, // skip if already in another sequence
},
);
return {
added: data.contacts?.length ?? 0,
alreadyInCampaign: data.contacts_already_in_campaign ?? 0,
errors: data.not_added_contact_ids ?? [],
};
}
// Mark contacts as finished or remove them from a sequence
export async function removeContactsFromSequence(
sequenceId: string,
contactIds: string[],
action: 'finished' | 'removed' = 'finished',
) {
const { data } = await client.post('/emailer_campaigns/remove_or_stop_contact_ids', {
emailer_campaign_id: sequenceId,
contact_ids: contactIds,
// "finished" marks contact as completed; "removed" fully removes
});
return {
updated: data.contacts?.length ?? 0,
};
}
Contacts must exist in your Apollo CRM before adding to sequences. Use the Contacts API to create them.
// Create a contact in your Apollo CRM
export async function createContact(params: {
firstName: string;
lastName: string;
email: string;
title?: string;
organizationName?: string;
websiteUrl?: string;
}) {
const { data } = await client.post('/contacts', {
first_name: params.firstName,
last_name: params.lastName,
email: params.email,
title: params.title,
organization_name: params.organizationName,
website_url: params.websiteUrl,
});
return {
id: data.contact.id,
email: data.contact.email,
name: `${data.contact.first_name} ${data.contact.last_name}`,
};
}
// Search your CRM contacts (not the Apollo database)
export async function searchCrmContacts(query: string) {
const { data } = await client.post('/contacts/search', {
q_keywords: query,
page: 1,
per_page: 25,
});
return data.contacts.map((c: any) => ({
id: c.id,
name: c.name,
email: c.email,
title: c.title,
company: c.organization_name,
}));
}
async function launchOutreach(
sequenceId: string,
leads: Array<{ firstName: string; lastName: string; email: string; title?: string; company?: string }>,
) {
// 1. Get a sending email account
const accounts = await getEmailAccounts();
const sender = accounts.find((a: any) => a.sendingEnabled);
if (!sender) throw new Error('No active email account found');
// 2. Create contacts in Apollo CRM (or find existing)
const contactIds: string[] = [];
for (const lead of leads) {
try {
const contact = await createContact({
firstName: lead.firstName,
lastName: lead.lastName,
email: lead.email,
title: lead.title,
organizationName: lead.company,
});
contactIds.push(contact.id);
} catch (err: any) {
// Contact may already exist — search for them
const existing = await searchCrmContacts(lead.email);
if (existing.length > 0) contactIds.push(existing[0].id);
}
}
// 3. Add contacts to the sequence
const result = await addContactsToSequence(sequenceId, contactIds, sender.id);
console.log(`Added ${result.added} contacts, ${result.alreadyInCampaign} already enrolled`);
return result;
}
POST /emailer_campaigns/searchGET /email_accountsPOST /emailer_campaigns/{id}/add_contact_idsPOST /emailer_campaigns/remove_or_stop_contact_idsPOST /contacts and search via POST /contacts/search| Error | Cause | Solution |
|---|---|---|
| 403 Forbidden | Standard API key used | Sequence endpoints require a master API key |
| No email accounts | Inbox not connected | Connect email at Settings > Channels > Email in Apollo UI |
| Contact already enrolled | Duplicate enrollment | Check contacts_already_in_campaign in response |
| Contact not found | ID does not exist in CRM | Create via POST /contacts first |
Proceed to apollo-common-errors for error handling patterns.
评论 (0)
暂无评论,成为第一个评论者吧!