Testing Clickup CLI
Run and manage tests for clickup-cli. Covers unit tests, e2e tests against a real ClickUp workspace, and the test data setup. Use when running tests, adding test coverage, debugging test failures, or setting up test fixtures.
Install
npx skills add krodak/clickup-cli --skill testing-clickup-cligit clone --depth 1 https://github.com/krodak/clickup-cli.git /tmp/clickup-cli
mkdir -p ~/.claude/skills
cp -r /tmp/clickup-cli/.agents/skills/testing-clickup-cli ~/.claude/skills/testing-clickup-cliPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Test Suite Overview | Suite | Command | Files | What it tests | | ----- | ------------------ | ------------------------- | ------------------------------------------------------------------ | | Unit | `npm test` | `tests/unit/**/*.test.ts` | All commands, API client, formatters, config. Mocks ClickUpClient. | | E2E | `npm run test:e2e` | `tests/e2e/**/*.e2e.ts` | Real API calls against a live ClickUp workspace. | Unit tests run in CI. E2E tests require `CLICKUP_API_TOKEN` in `.env.test` and are not part of CI. ## Running Tests ```bash npm test # all unit tests npm test -- tests/unit/commands/ # just command tests npm test -- -t "sprint" # filter by test name npm run test:e2e # e2e tests (needs .env.test) ``` The unit test global setup runs `npm run build` before tests start. ## E2E Test Workspace Tests run against the personal ClickUp workspace (profile: `personal`). ### Space: E2E Tests (90166622768) Pre-populated with test fixtures: | Fixture | What it contains | | ------------------ | ----------------------------------------------------------------------------- | | **Sprints folder** | 3 sprint lists with `(M/DD - M/DD)` date ranges. Sprint 2 is "current". |
Details
- Skill name
testing-clickup-cli- Repository
- krodak/clickup-cli
- Path
.agents/skills/testing-clickup-cli/SKILL.md- License
- MIT
- Repo updated
- 10 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Testing Clickup CLI skill do?
Run and manage tests for clickup-cli. Covers unit tests, e2e tests against a real ClickUp workspace, and the test data setup. Use when running tests, adding test coverage, debugging test failures, or setting up test fixtures.
How do I install the Testing Clickup CLI skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add krodak/clickup-cli --skill testing-clickup-cli. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Testing Clickup CLI popular?
It lives in krodak/clickup-cli, which has 132 GitHub stars and 21 forks, and is included in 1 curated skill list.
Related skills
Clickup
132krodak/clickup-cli
Use when reading or changing anything in ClickUp via the `cup` CLI - tasks, sprints, comments, Docs, Chat, views, webhooks, or workspace structure. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries, searching tasks, checking overdue items, assigning tasks, ClickUp Docs and doc pages (read, create, edit), ClickUp Chat channels and messages, views and view tasks, webhooks, exporting or archiving ClickUp data (knowledge transfer, off-boarding), creating or renaming spaces, folders, and lists, list templates, opening t
Releasing Clickup CLI
132krodak/clickup-cli
Publishes a new version of clickup-cli to npm, updates Homebrew tap, writes release notes, and syncs the agent skill. Use when releasing a new version, bumping version, or verifying a release.
Openspec Plus TDD
218sudokar/openspec-plus
MANDATORY skill that activates whenever code is written to implement an OpenSpec change task. Triggers: openspec-plus-apply is active, /opsx-apply is running, the user is implementing tasks from an OpenSpec change, an implementer subagent dispatched by openspec-plus-apply is starting work, or the user invokes phrases like 'TDD for the change', 'implementing change tasks', or 'writing tests for spec scenarios'. Load before any production code is written for an OpenSpec change. Enforces strict RED-GREEN-REFACTOR per test (any test — acceptance, unit, edge case, helper). Iron Law: NO PRODUCTION C
Databricks Synthetic Data Gen
407databricks/databricks-agent-skills
Generate realistic synthetic data using Spark + Faker (strongly recommended). Supports serverless execution, multiple output formats (Parquet/JSON/CSV/Delta), and scales from thousands to millions of rows. For small datasets (<10K rows), can optionally generate locally and upload to volumes. Use when user mentions 'synthetic data', 'test data', 'generate data', 'demo dataset', 'Faker', or 'sample data'.
Playwright
398JetBrains/skills
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
Fix Flaky Tests
280intercom/2x-skills
Investigate and fix flaky or intermittently-failing tests in any framework and CI system — detects the framework, CI provider, and app profile, then applies the matching classification and fix patterns. Triggers on a flaky-test issue or CI URL, a test that "passes on retry" or "fails in CI but passes locally", a bot that skipped a test, or a request to reopen or dispute the closure or diagnosis of a flaky-test issue (for that case open the issue first; its title or label confirms scope even when the prompt has no flaky-test keywords).
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.