SkillAtlasSkill 详情

clickup-ci-integration

A model-agnostic agent-skills platform.

审核状态:已审核Quality 72Security 70

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件:README.md

抓取于 2026年9月2日

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.

Release CLI Plugins Skills GitHub Stars skills.sh Sponsor: Kobiton Buy me a monster

ko-fi

Version semantics: the release badge is this marketplace's display version. npm packages, including the ccpi CLI 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."

CountCohortReproduce with
440catalog plugins (catalog-entry cohort)node scripts/generate-readme-toc.mjs over marketplace.extended.json
2,984marketplace-visible skills (distinct)node -e "import('./scripts/corpus-resolver.mjs').then(m=>console.log(m.resolveCorpus('marketplace-visible').length))"
347agent definitions in pluginsgit ls-files 'plugins/**' | grep '/agents/.*\.md'
19plugin categoriesls -d plugins/*/

📦 Live npm Downloads

Across 394 published packages in the claude-code-plugins namespace. Updated daily by GitHub Actions.

WindowAll packagesEstablished (>30d)
Last 24 hours641641
Last 7 days3,2723,272
Last 30 days11,79411,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:

#PackageLast 30d
1@intentsolutionsio/openrouter-pack1,026
2@intentsolutionsio/groq-pack734
3@intentsolutionsio/mistral-pack264
4@intentsolutionsio/databricks-pack216
5@intentsolutionsio/wallet-security-auditor211
6@intentsolutionsio/shopify-pack155
7@intentsolutionsio/openbb-terminal151
8@intentsolutionsio/ccpi139
9@intentsolutionsio/penetration-tester125
10@intentsolutionsio/langchain-py-pack121

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:

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).

CategoryPlugins
🤖AI & Machine Learning37
🎭AI Agents & Agency9
🔌API Development26
💼Business Tools6
👥Community20
₿Crypto & Web327
💾Database26
🎨Design2
🔧DevOps & Infrastructure36
📚Examples & Templates5
🧩MCP Servers17
📦Packages5
⚡Performance25
✅Productivity29
🎁SaaS Skill Packs105
🔐Security27
✨Skill Enhancers9
🧪Testing28
📁Analytics1

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:

ClassWhat it isHow the reader can tell
Canonical skillFirst-party, harness-free, the source of truthNo .source.json in its plugin directory
Generated adapterA thin, machine-produced harness projectionLives under a generated path with a "generated — do not edit" header
First-party packageAn Intent Solutions distribution (npm, cowork zip)@intentsolutionsio scope, IS-authored license
Upstream mirrorSomebody 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:

Governance

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 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
  3. 将 "skills/.curated/clickup-ci-integration" 文件夹复制到 Codex 的 skills 目录中。
  4. 重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Codex 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
  3. 将 "skills/.curated/clickup-ci-integration" 文件夹复制到 Claude Code 的 skills 目录中。
  4. 重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Claude Code 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
  3. 将 "skills/.curated/clickup-ci-integration" 文件夹复制到 Cursor 的 skills 目录中。
  4. 重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Cursor 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
  3. 将 "skills/.curated/clickup-ci-integration" 文件夹复制到 GitHub Copilot 的 skills 目录中。
  4. 重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/jeremylongshore/tons-of-skills-marketplace.git
  3. 将 "skills/.curated/clickup-ci-integration" 文件夹复制到 Windsurf 的 skills 目录中。
  4. 重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Windsurf 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
name: clickup-ci-integration
description: 'Set up CI/CD pipelines for ClickUp API integrations with GitHub Actions,

  automated testing, and task status sync.

  Trigger: "clickup CI", "clickup GitHub Actions", "clickup automated tests",

  "CI clickup integration", "clickup pipeline", "clickup CI/CD".

  '
allowed-tools: Read, Write, Edit, Bash(gh:*)
version: 1.6.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- productivity
- clickup
compatibility: Designed for Claude Code

ClickUp CI Integration

Overview

Automate ClickUp integration testing in CI and sync task statuses from your pipeline. Uses GitHub Actions with live API testing against ClickUp API v2.

Prerequisites

  • Protected CI environment with a scoped, masked ClickUp secret
  • Mock fixtures for pull requests and an isolated task/list for live tests
  • A bounded cleanup strategy and environment approval for any status update
  • Artifact/log retention policy that excludes task content and credentials

Instructions

Run mocks and schema checks on every change, reserve live API tests for the protected integration environment, and create only identifiable disposable tasks. Verify cleanup and status transitions after each run; a failed cleanup, permission mismatch, or rate-limit response fails the workflow rather than being ignored or retried with a broader token.

GitHub Actions Workflow

# .github/workflows/clickup-integration.yml
name: ClickUp Integration Tests

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  unit-tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm test -- --coverage

  integration-tests:
    runs-on: ubuntu-latest
    needs: unit-tests
    env:
      CLICKUP_API_TOKEN: ${{ secrets.CLICKUP_API_TOKEN }}
      CLICKUP_TEST_LIST_ID: ${{ secrets.CLICKUP_TEST_LIST_ID }}
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - name: ClickUp API health check
        run: |
          STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
            https://api.clickup.com/api/v2/user \
            -H "Authorization: $CLICKUP_API_TOKEN")
          if [ "$STATUS" != "200" ]; then
            echo "::warning::ClickUp API returned $STATUS, skipping integration tests"
            exit 0
          fi
      - name: Run integration tests
        run: CLICKUP_LIVE=1 npm run test:integration

Configure Secrets

# Store ClickUp token in GitHub Secrets
gh secret set CLICKUP_API_TOKEN --body "pk_12345678_YOUR_TOKEN"

# Store test list ID (for integration tests to create/delete test tasks)
gh secret set CLICKUP_TEST_LIST_ID --body "900100200300"

Integration Test Suite

// tests/integration/clickup-ci.test.ts
import { describe, it, expect, afterAll } from 'vitest';

const TOKEN = process.env.CLICKUP_API_TOKEN!;
const TEST_LIST = process.env.CLICKUP_TEST_LIST_ID!;
const BASE = 'https://api.clickup.com/api/v2';
const createdTaskIds: string[] = [];

async function api(path: string, options?: RequestInit) {
  const res = await fetch(`${BASE}${path}`, {
    ...options,
    headers: { 'Authorization': TOKEN, 'Content-Type': 'application/json', ...options?.headers },
  });
  return { status: res.status, data: await res.json() };
}

describe('ClickUp API Integration', () => {
  it('authenticates successfully', async () => {
    const { status, data } = await api('/user');
    expect(status).toBe(200);
    expect(data.user.id).toBeDefined();
  });

  it('creates a task in test list', async () => {
    const { status, data } = await api(`/list/${TEST_LIST}/task`, {
      method: 'POST',
      body: JSON.stringify({
        name: `CI Test Task - ${new Date().toISOString()}`,
        description: 'Created by CI pipeline, safe to delete',
        priority: 4,
      }),
    });
    expect(status).toBe(200);
    expect(data.id).toBeDefined();
    createdTaskIds.push(data.id);
  });

  it('reads the created task', async () => {
    const { status, data } = await api(`/task/${createdTaskIds[0]}`);
    expect(status).toBe(200);
    expect(data.name).toContain('CI Test Task');
  });

  afterAll(async () => {
    // Cleanup: delete test tasks
    for (const id of createdTaskIds) {
      await api(`/task/${id}`, { method: 'DELETE' });
    }
  });
});

Sync CI Status to ClickUp Task

// scripts/update-clickup-task.ts
// Run after deploy: npx tsx scripts/update-clickup-task.ts TASK_ID "deployed"
async function updateTaskFromCI(taskId: string, newStatus: string) {
  const response = await fetch(
    `https://api.clickup.com/api/v2/task/${taskId}`,
    {
      method: 'PUT',
      headers: {
        'Authorization': process.env.CLICKUP_API_TOKEN!,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({ status: newStatus }),
    }
  );

  if (!response.ok) {
    console.error(`Failed to update task ${taskId}:`, await response.text());
    process.exit(1);
  }
  console.log(`Task ${taskId} status updated to "${newStatus}"`);
}

const [taskId, status] = process.argv.slice(2);
updateTaskFromCI(taskId, status);

Error Handling

IssueCauseSolution
Secret not foundMissing GitHub secretgh secret set CLICKUP_API_TOKEN
401 in CIToken expired/rotatedUpdate secret value
Rate limited in CIToo many test runsAdd pre-flight rate check
Integration test cleanup failsTask already deletedIgnore 404 on cleanup

Output

Publish a redacted CI receipt containing fixture/API test result, disposable task IDs, cleanup result, rate-limit state, workflow URL, and promotion decision. Keep tokens, task descriptions, private comments, and member data out of logs and artifacts.

Examples

On a protected branch, create one labeled test task in an isolated list, verify the expected status update, then delete it and prove it is absent. If cleanup does not complete or the secret is unavailable, fail the run and notify the integration owner instead of leaving production-like tasks behind.

Resources

Next Steps

For deployment patterns, see clickup-deploy-integration.

发现问题?提交给管理员复核

评分:

评论 (0)

暂无评论,成为第一个评论者吧!