Novu Design Workflow
novuhq/novu
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.
Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets.
Install Clickup Debug Bundle
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickup-debug-bundle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/clickup-debug-bundle .claude/skills/clickup-debug-bundle && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "clickup-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clickup-debug-bundle into .claude/skills/clickup-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickup-debug-bundle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clickup-debug-bundleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickup-debug-bundle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/clickup-debug-bundle .agents/skills/clickup-debug-bundle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clickup-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clickup-debug-bundle into .agents/skills/clickup-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickup-debug-bundle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickup-debug-bundle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/clickup-debug-bundle .cursor/skills/clickup-debug-bundle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clickup-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clickup-debug-bundle into .cursor/skills/clickup-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickup-debug-bundle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/clickup-debug-bundle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickup-debug-bundle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/clickup-debug-bundle .gemini/skills/clickup-debug-bundle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clickup-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clickup-debug-bundle into .gemini/skills/clickup-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickup-debug-bundle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickup-debug-bundleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/clickup-debug-bundle .github/skills/clickup-debug-bundle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clickup-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clickup-debug-bundle into .github/skills/clickup-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickup-debug-bundle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clickup-debug-bundle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/clickup-debug-bundle .opencode/skills/clickup-debug-bundle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clickup-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clickup-debug-bundle into .opencode/skills/clickup-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clickup-debug-bundle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
clickup-debug-bundle- GitHub stars
- 2.8k
- Token cost
- ~997 tokens
- SKILL.md length
- 392 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets.
- Works in 6 steps: Confirm incident scope, collection… → Inspect local configuration names and… → Run bounded read-only identity/workspace… → …
- Escalating a ClickUp API incident
- SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clickup Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets. Use when escalating a ClickUp API incident. Trigger with "ClickUp debug bundle", "ClickUp diagnostics", or "collect ClickUp evidence".
Its SKILL.md is about 1000 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live collection requires authorized ClickUp access and local retention controls
It sits in Backend & APIs, covering Webhooks. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Escalating a ClickUp API incident
- With ClickUp debug bundle
- ClickUp diagnostics
- Collect ClickUp evidence
Example prompts
- “ClickUp debug bundle”
- “ClickUp diagnostics”
- “collect ClickUp evidence”
- “/clickup-debug-bundle”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; live collection requires authorized ClickUp access and local retention controls
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Confirm incident scope, collection owner, field allow-list, output path, and deletion deadline.
- Inspect local configuration names and versions without printing values.
- Run bounded read-only identity/workspace and status probes; capture only approved metadata.
- Record sanitized rate headers, status codes, timings, schema digests, and local adapter versions.
- Scan the bundle for credential and content patterns; require human review before sharing.
- Hash, transfer through the approved channel, and delete or retain on schedule.
What it can do on your machine
Read from SKILL.md and the folder at commit 23ea8d4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWebFetchWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developer.clickup.comstatus.clickup.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code; live collection requires authorized ClickUp access and local retention controls
From compatibility in the SKILL.md frontmatter.
Context cost
Clickup Debug Bundle loads about 997 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 392 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit 23ea8d4, republished under its MIT licence (© jeremylongshore). 392 words, ~997 tokens.
Download SKILL.mdSave it as
.claude/skills/clickup-debug-bundle/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- clickup-debug-bundle
- description
- Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets. Use when escalating a ClickUp API incident. Trigger with "ClickUp debug bundle", "ClickUp diagnostics", or "collect ClickUp evidence".
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code; live collection requires authorized ClickUp access and local retention controls
- argument-hint
- [incident-id] [output-directory]
- version
- 1.8.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, clickup, diagnostics
- model
- inherit
- effort
- high
ClickUp Redacted Diagnostic Bundle
Overview
Create supportable evidence while preventing a troubleshooting artifact from becoming a second sensitive-data store. Make every included field explainable to the named reviewer.
Prerequisites
- An incident identifier, approved output directory, retention deadline, and named reviewer
- A scoped credential stored outside command history and artifact content
- An allow-list of read-only probes and fields
Tool Discipline
Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode.
Current Contract
- Useful evidence includes status, endpoint version, latency, response type, sanitized error code, and rate headers.
GET /api/v2/userandGET /api/v2/teamcan prove identity and authorized Workspaces without reading task content.- Provider status is separate from tenant authorization and application behavior.
- Authorization headers, response bodies, user emails, task names, comments, attachments, and webhook secrets are excluded.
Authentication
Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret.
Show full SKILL.md (193 more words)Show less
Instructions
- Confirm incident scope, collection owner, field allow-list, output path, and deletion deadline.
- Inspect local configuration names and versions without printing values.
- Run bounded read-only identity/workspace and status probes; capture only approved metadata.
- Record sanitized rate headers, status codes, timings, schema digests, and local adapter versions.
- Scan the bundle for credential and content patterns; require human review before sharing.
- Hash, transfer through the approved channel, and delete or retain on schedule.
Approval Boundaries
Do not add raw headers, full environment dumps, task payloads, member records, or attachments to make the bundle more convenient.
Output
Return bundle path, SHA-256, included field classes, excluded classes, scan result, reviewer, sharing decision, and deletion deadline.
Error Handling
| Condition | Response |
|---|---|
| Redaction scan finds a secret | Do not share; quarantine, rotate, and regenerate. |
| Probe would read work content | Skip it and record the evidence gap. |
| Output directory is uncontrolled | Refuse collection until a governed location exists. |
| Incident scope expands | Obtain a new collection approval. |
Examples
The example below is a redacted operator receipt; it contains no task text, member data, credential, or webhook secret.
incident=CU-142; probes=3; task-bodies=0; secrets=0; sha256=recorded; review=approved; delete-by=2026-09-17Resources
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/.curated/clickup-debug-bundle of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit 23ea8d4
Compare with similar skills
Clickup Debug Bundle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clickup Debug Bundle this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~997 | Automated safety check: Pass | MIT | |
| Novu Design Workflownovuhq/novu | 40k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Stripe Appsfossasia/eventyay | 1.7k | 2 repos | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Golivemikehasa/golive-skill | 1.2k | — | ~13k | Automated safety check: Notes | MIT | |
| Dingtalk Messageagentscope-ai/ReMe | 3.6k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| PR Review Provideryansongda/pay | 5.4k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Stripe Apps
fossasia/eventyay
A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.
Golive
mikehasa/golive-skill
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS).
Dingtalk Message
agentscope-ai/ReMe
钉钉消息发送技能。支持企业内部机器人（批量单聊/群聊）和 Webhook 自定义机器人两种接入方式，支持多机器人管理，支持文本、Markdown、链接、ActionCard、FeedCard等多种消息类型。
PR Review Provider
yansongda/pay
A skill your agent uses when reviewing PRs that add or modify a payment Provider in yansongda/pay - covers plugin pipeline, multi-tenant safety, signature verification, docs, and naming conventions.
Stripe Best Practices
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Analyzing Text With NLP
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to perform natural language processing and text analysis using the nlp-text-analyzer plugin.
Building Neural Networks
jeremylongshore/tons-of-skills-marketplace
Execute this skill allows AI assistant to construct and configure neural network architectures using the neural-network-builder plugin.
Detecting Data Anomalies
jeremylongshore/tons-of-skills-marketplace
Process identify anomalies and outliers in datasets using machine learning algorithms.
Explaining Machine Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill enables AI assistant to provide interpretability and explainability for machine learning models.
Optimizing Prompts
jeremylongshore/tons-of-skills-marketplace
Execute this skill optimizes prompts for large language models (llms) to reduce token usage, lower costs, and improve performance.
Related
Categories
Questions about Clickup Debug Bundle
What does Clickup Debug Bundle do?
Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets. Clickup Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Collect a minimal redacted ClickUp connectivity and contract bundle without task bodies, tokens, or webhook secrets.
When should I use Clickup Debug Bundle?
Clickup Debug Bundle fits situations like: escalating a ClickUp API incident; with ClickUp debug bundle; clickUp diagnostics; collect ClickUp evidence.
How do I install Clickup Debug Bundle in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a claude-code`. Or copy the skill folder (skills/.curated/clickup-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clickup-debug-bundle in your project. Claude Code loads it when a task matches its description.
How do I install Clickup Debug Bundle in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a codex`. Or copy the skill folder (skills/.curated/clickup-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clickup-debug-bundle in your project. Codex loads it when a task matches its description.
Can I use Clickup Debug Bundle in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clickup-debug-bundle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clickup-debug-bundle, .gemini/skills/clickup-debug-bundle, .github/skills/clickup-debug-bundle and .opencode/skills/clickup-debug-bundle in your project.
What does Clickup Debug Bundle need to run?
SKILL.md names no scripts, command-line tools or credentials: Clickup Debug Bundle is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live collection requires authorized ClickUp access and local retention controls.
Does Clickup Debug Bundle access the network?
SKILL.md names 2 domains. As links in the text: developer.clickup.com and status.clickup.com. This is read from the text; nothing was executed.
Is Clickup Debug Bundle safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Clickup Debug Bundle use?
Clickup Debug Bundle is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Clickup Debug Bundle use?
About 997 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 584 tokens, read only when the agent opens those files.
What are the alternatives to Clickup Debug Bundle?
Skills that share tags, products or a category with Clickup Debug Bundle: Novu Design Workflow (novuhq/novu, 40k stars), Stripe Apps (fossasia/eventyay, 1.7k stars), Golive (mikehasa/golive-skill, 1.2k stars) and Dingtalk Message (agentscope-ai/ReMe, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clickup Debug Bundle?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,821 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 8, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.