复制安装命令
用 Codex 或 Claude 安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
SkillAtlasSkill 详情
clay-upgrade-migration
A model-agnostic agent-skills platform.
审核状态：已审核Quality 72Security 70
项目 README
来源文件：README.md
Tons of Skills
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.
Version semantics: the release badge is this marketplace's display version. npm packages, including the
ccpiCLI and publishable plugins, retain their own package versions; they are intentionally not expected to equal the display version. The version-surface checker governs the display surfaces without rewriting package semver.
Install
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, code-cleanup, web-analytics, token-optimizer, executive-assistant-skills, skill-creator, cursor-pack, crypto-portfolio-tracker. See all at tonsofskills.com.
Scale, labeled
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 |
|---|---|---|
| 440 | catalog plugins (catalog-entry cohort) | node scripts/generate-readme-toc.mjs over marketplace.extended.json |
| 2,984 | 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/*/ |
📦 Live npm Downloads
Across 394 published packages in the claude-code-plugins namespace. Updated daily by GitHub Actions.
| Window | All packages | Established (>30d) |
|---|---|---|
| Last 24 hours | 641 | 641 |
| Last 7 days | 3,272 | 3,272 |
| Last 30 days | 11,794 | 11,794 |
"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-09-02T04:55:57.759Z.
Ways in
Five real questions, five doors — each resolves to a live, generated surface, never a hand-maintained list:
- By category — the table below, regenerated from the catalog on every sync.
- By plugin — tonsofskills.com/explore, the full browsable catalog.
- By skill — tonsofskills.com/skills, searchable across the whole corpus.
- By job to be done — tonsofskills.com/cowork, curated bundles as one-click downloads.
- By certification tier — the Certification section below, rendered from the live report.
Browse by category
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 | 37 |
| 🎭 | AI Agents & Agency | 9 |
| 🔌 | API Development | 26 |
| 💼 | Business Tools | 6 |
| 👥 | Community | 20 |
| ₿ | Crypto & Web3 | 27 |
| 💾 | Database | 26 |
| 🎨 | Design | 2 |
| 🔧 | DevOps & Infrastructure | 36 |
| 📚 | Examples & Templates | 5 |
| 🧩 | MCP Servers | 17 |
| 📦 | Packages | 5 |
| ⚡ | Performance | 25 |
| ✅ | Productivity | 29 |
| 🎁 | SaaS Skill Packs | 105 |
| 🔐 | Security | 27 |
| ✨ | Skill Enhancers | 9 |
| 🧪 | Testing | 28 |
| 📁 | Analytics | 1 |
What the classes mean
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 |
Certification
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.
Contribute
Start with the contribution guide, then the intake and review standards every submission passes through:
- Contribution requirements — including the AI-assistance disclosure expectation.
- Skill submission intake standard — the tiered document matrix new plugins ship with.
- External-PR review standard — how maintainers triage and what gets a submission merged.
Governance
- STANDARDS.md — the public spec posture and the canonical-documents index (one owner per fact class).
- The platform master blueprint — CI gates, release, docs governance, and this README's own landing contract.
- GOVERNANCE.md · SECURITY.md · LICENSE
Provenance
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.
License
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.
其他
中风险
- 来源需自行核对维护者身份。
- 包含脚本或命令调用，安装前请复核。
- 可能需要外部 token、网络权限或第三方服务。
- 未检测到高风险命令。
- 扫描发现：3 条。
Codex — Git Clone 安装
- 安装前请先查看来源仓库和风险报告。
- 克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
- 将 "skills/.curated/clay-upgrade-migration" 文件夹复制到 Codex 的 skills 目录中。
- 重启 Codex 让新的 skill 生效。
Codex — 手动复制安装
- 安装前请先查看来源仓库和风险报告。
- 从源仓库下载 SKILL.md 及相关文件。
- 在 Codex 的 skills 目录中创建新文件夹。
- 将所有 skill 文件复制到新文件夹中。
- 重启 Codex 让新的 skill 生效。
Claude Code — Git Clone 安装
- 安装前请先查看来源仓库和风险报告。
- 克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
- 将 "skills/.curated/clay-upgrade-migration" 文件夹复制到 Claude Code 的 skills 目录中。
- 重启 Claude Code 让新的 skill 生效。
Claude Code — 手动复制安装
- 安装前请先查看来源仓库和风险报告。
- 从源仓库下载 SKILL.md 及相关文件。
- 在 Claude Code 的 skills 目录中创建新文件夹。
- 将所有 skill 文件复制到新文件夹中。
- 重启 Claude Code 让新的 skill 生效。
Cursor — Git Clone 安装
- 安装前请先查看来源仓库和风险报告。
- 克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
- 将 "skills/.curated/clay-upgrade-migration" 文件夹复制到 Cursor 的 skills 目录中。
- 重启 Cursor 让新的 skill 生效。
Cursor — 手动复制安装
- 安装前请先查看来源仓库和风险报告。
- 从源仓库下载 SKILL.md 及相关文件。
- 在 Cursor 的 skills 目录中创建新文件夹。
- 将所有 skill 文件复制到新文件夹中。
- 重启 Cursor 让新的 skill 生效。
GitHub Copilot — Git Clone 安装
- 安装前请先查看来源仓库和风险报告。
- 克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
- 将 "skills/.curated/clay-upgrade-migration" 文件夹复制到 GitHub Copilot 的 skills 目录中。
- 重启 GitHub Copilot 让新的 skill 生效。
GitHub Copilot — 手动复制安装
- 安装前请先查看来源仓库和风险报告。
- 从源仓库下载 SKILL.md 及相关文件。
- 在 GitHub Copilot 的 skills 目录中创建新文件夹。
- 将所有 skill 文件复制到新文件夹中。
- 重启 GitHub Copilot 让新的 skill 生效。
Windsurf — Git Clone 安装
- 安装前请先查看来源仓库和风险报告。
- 克隆仓库：git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
- 将 "skills/.curated/clay-upgrade-migration" 文件夹复制到 Windsurf 的 skills 目录中。
- 重启 Windsurf 让新的 skill 生效。
Windsurf — 手动复制安装
- 安装前请先查看来源仓库和风险报告。
- 从源仓库下载 SKILL.md 及相关文件。
- 在 Windsurf 的 skills 目录中创建新文件夹。
- 将所有 skill 文件复制到新文件夹中。
- 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
name: clay-upgrade-migration
description: 'Navigate Clay plan changes, pricing migrations, and feature upgrades.
Use when upgrading Clay plans, migrating to the 2026 pricing model,
or adapting integrations to new Clay features.
Trigger with phrases like "upgrade clay", "clay migration", "clay pricing change",
"clay plan upgrade", "clay new pricing".
'
allowed-tools: Read, Write, Edit, Bash(curl:*), Grep
version: 1.14.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- clay
- api
- migration
compatibility: Designed for Claude CodeClay Upgrade & Migration
Overview
Guide for navigating Clay plan upgrades and the March 2026 pricing overhaul. Clay restructured from Starter/Explorer/Pro to Launch/Growth tiers, split credits into Data Credits + Actions, and cut data costs 50-90%. This skill covers migration decisions, integration impact, and adaptation strategies.
Prerequisites
- Active Clay account
- Understanding of current credit consumption
- Access to Clay billing dashboard
Instructions
Step 1: Understand the 2026 Pricing Change
Old Plans (Legacy -- available until April 10, 2026):
| Plan | Price | Credits | Key Limits |
|---|---|---|---|
| Starter | $149/mo | Limited | No HTTP API, no webhooks |
| Explorer | $349/mo | 25K | 400 records/hour throttle |
| Pro | $800/mo | 50K | HTTP API, webhooks, priority support |
New Plans (March 2026+):
| Plan | Price | Data Credits | Actions | Key Features |
|---|---|---|---|---|
| Launch | $185/mo | 2,500 | 15,000 | Phone enrichment, signal tracking |
| Growth | $495/mo | 6,000 | 40,000 | CRM sync, HTTP API, web intent, ads |
Key changes:
- Credits split into Data Credits (buying enrichment data) and Actions (using the platform)
- Data costs cut 50-90% (each enrichment is cheaper)
- No enrichment charges on failed lookups (no data = no charge)
- Credit rollover capped at 2x monthly limit
Step 2: Audit Your Current Usage
# Check current plan and credit usage from Clay dashboard
# Navigate to Settings > Plans & Billing
# Record:
# - Current plan tier
# - Monthly credits used (average over 3 months)
# - Which enrichment providers consume most credits
# - Whether you use HTTP API columns
# - Whether you use webhook sources
Decision matrix for migration:
| If you currently... | Recommended new plan |
|---|---|
| Use < 2,500 data credits/mo | Launch ($185) |
| Need HTTP API columns | Growth ($495) |
| Need CRM sync | Growth ($495) |
| Use webhooks + high volume | Growth ($495) |
| Stay on legacy Explorer | Keep legacy if 400/hr limit works |
| Have Enterprise contract | Contact Clay sales |
Step 3: Adapt Integration Code for New Credit Model
// src/clay/credit-tracker.ts — track new split credit model
interface CreditUsage {
dataCredits: { used: number; limit: number; rolloverMax: number };
actions: { used: number; limit: number };
}
class CreditTracker {
private usage: CreditUsage;
constructor(plan: 'launch' | 'growth') {
this.usage = plan === 'launch'
? { dataCredits: { used: 0, limit: 2500, rolloverMax: 5000 }, actions: { used: 0, limit: 15000 } }
: { dataCredits: { used: 0, limit: 6000, rolloverMax: 12000 }, actions: { used: 0, limit: 40000 } };
}
recordEnrichment(dataCreditsUsed: number) {
this.usage.dataCredits.used += dataCreditsUsed;
this.usage.actions.used += 1; // Each enrichment = 1 action
if (this.usage.dataCredits.used > this.usage.dataCredits.limit * 0.8) {
console.warn(`Data credits at ${((this.usage.dataCredits.used / this.usage.dataCredits.limit) * 100).toFixed(0)}% of monthly limit`);
}
}
canAfford(estimatedCredits: number): boolean {
return (
this.usage.dataCredits.used + estimatedCredits <= this.usage.dataCredits.limit &&
this.usage.actions.used + 1 <= this.usage.actions.limit
);
}
}
Step 4: Optimize for the New Model
No-charge on failed lookups changes the cost equation:
// Old model: every enrichment attempt cost credits, even if no data returned
// New model: only charged when data is actually returned
// This makes wider waterfall enrichments cheaper:
// Before: 5-provider waterfall = 5 charges even if only 1 finds data
// After: 5-provider waterfall = 1 charge if only 1 finds data
// Strategy: wider waterfalls are now more cost-effective
Connect your own API keys for maximum savings:
| Provider | Clay Credits (managed) | Own Key |
|---|---|---|
| Apollo | 2 data credits | 0 credits |
| Clearbit | 2-5 data credits | 0 credits |
| Hunter | 2 data credits | 0 credits |
| ZoomInfo | 5-13 data credits | 0 credits |
Step 5: Migrate Webhook Integrations
If moving from a plan without webhooks to one with them (or vice versa):
# Test webhook availability on new plan
curl -X POST "$CLAY_WEBHOOK_URL" \
-H "Content-Type: application/json" \
-d '{"migration_test": true, "timestamp": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
# Verify HTTP API columns still work after plan change
# HTTP API columns are only available on Growth plan
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Features disappeared | Downgraded plan | Check feature availability per tier |
| HTTP API columns disabled | Moved to Launch (no HTTP API) | Upgrade to Growth or use webhooks only |
| Higher credit usage than expected | Actions now counted separately | Monitor both Data Credits and Actions |
| Webhook stopped working | Plan change affected access | Verify webhook feature on current plan |
Output
Create a migration receipt with source and target plan/features, affected tables and integrations, projected and observed credit use, staging evidence, production approval, and rollback result. Pricing or feature documentation is not a deployment guarantee; retain the old working configuration until the new path is proven against the intended workspace.
Examples
Test a plan-related webhook change against a staging table with a synthetic row, confirm authentication, idempotency, and downstream delivery, then compare credit consumption to the documented baseline. If a required feature is absent or a callback fails, restore the former integration and delay the cutover rather than attempting a live workaround.
Resources
Next Steps
For CI integration during upgrades, see clay-ci-integration.
评论 (0)
暂无评论，成为第一个评论者吧！