Debug
asgeirtj/system_prompts_leaks
Enable debug logging for this session and help diagnose issues
Analyze a Clari incident and collect a minimal support bundle with job timelines, contract fingerprints, and secret-safe evidence.
MITAuto-check passed
Install Clari Debug Bundle
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clari-debug-bundle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clari-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/clari-debug-bundle .claude/skills/clari-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 "clari-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clari-debug-bundle into .claude/skills/clari-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clari-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/clari-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 clari-debug-bundle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clari-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/clari-debug-bundle .agents/skills/clari-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 "clari-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clari-debug-bundle into .agents/skills/clari-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clari-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 clari-debug-bundle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clari-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/clari-debug-bundle .cursor/skills/clari-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 "clari-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clari-debug-bundle into .cursor/skills/clari-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clari-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/clari-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 clari-debug-bundle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clari-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/clari-debug-bundle .gemini/skills/clari-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 "clari-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clari-debug-bundle into .gemini/skills/clari-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clari-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 clari-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 clari-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/clari-debug-bundle .github/skills/clari-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 "clari-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clari-debug-bundle into .github/skills/clari-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clari-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 clari-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 clari-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/clari-debug-bundle .opencode/skills/clari-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 "clari-debug-bundle" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clari-debug-bundle into .opencode/skills/clari-debug-bundle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clari-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
clari-debug-bundle- GitHub stars
- 2.8k
- Token cost
- ~1k tokens
- SKILL.md length
- 425 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze a Clari incident and collect a minimal support bundle with job timelines, contract fingerprints, and secret-safe evidence.
- Works in 6 steps: Create the manifest → Collect control-plane evidence → Collect data-plane summaries → …
- Escalating a provider
- SKILL.md covers Overview, Prerequisites, Instructions and Authentication, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clari Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze a Clari incident and collect a minimal support bundle with job timelines, contract fingerprints, and secret-safe evidence. Use when escalating a provider or pipeline failure. Trigger with: "collect Clari diagnostics", "build a Clari support bundle", "redact a Clari incident".
Its SKILL.md is about 1k 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: Requires an incident identifier, authorized time window, redaction policy, and an encrypted evidence destination.
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 provider
- Pipeline failure
- With: collect Clari diagnostics
- Build a Clari support bundle
Example prompts
- “collect Clari diagnostics”
- “build a Clari support bundle”
- “redact a Clari incident”
- “/clari-debug-bundle”
Requirements
- Compatibility (from SKILL.md): Requires an incident identifier, authorized time window, redaction policy, and an encrypted evidence destination.
- Pre-approved tools (allowed-tools): Read, Grep, Write, Edit
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. 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:
ReadGrepWriteEdit
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.clari.comapi-doc.copilot.clari.comclari.statuspage.io
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
Requires an incident identifier, authorized time window, redaction policy, and an encrypted evidence destination.
From compatibility in the SKILL.md frontmatter.
Context cost
Clari Debug Bundle loads about 1k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 425 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 cfae287, republished under its MIT licence (© jeremylongshore). 425 words, ~1,042 tokens.
Download SKILL.mdSave it as
.claude/skills/clari-debug-bundle/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- clari-debug-bundle
- description
- Analyze a Clari incident and collect a minimal support bundle with job timelines, contract fingerprints, and secret-safe evidence. Use when escalating a provider or pipeline failure. Trigger with: "collect Clari diagnostics", "build a Clari support bundle", "redact a Clari incident".
- allowed-tools
- Read, Grep, Write, Edit
- compatibility
- Requires an incident identifier, authorized time window, redaction policy, and an encrypted evidence destination.
- version
- 2.0.0
- argument-hint
- [surface-incident-id-and-time-window]
- model
- inherit
- effort
- high
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- saas, clari, diagnostics, support, redaction
Clari Redacted Support Bundle
Overview
A useful support bundle explains what happened without copying credentials or customer payloads. Collect identifiers, timing, states, hashes, schema summaries, and controlled samples under a manifest that is reviewable before sharing.
Prerequisites
- Incident ID, owner, environment, surface, and affected window
- Exact endpoint and method inventory plus provider job IDs or cursors
- Approved redaction rules, retention, and sharing destination
Instructions
Step 1: Create the manifest
Record collector version, contract fingerprint, host, endpoint names, request fingerprints, timestamps, and system versions.
Step 2: Collect control-plane evidence
Capture HTTP statuses, redacted response headers, error codes or IDs, job state transitions, attempts, waits, and scheduler ownership.
Step 3: Collect data-plane summaries
Record content type, byte and row counts, field names, schema hash, and reconciliation deltas without raw revenue, identity, transcript, or recording data.
Step 4: Collect local health
Include deployment version, checkpoint state, queue depth, destination health, and relevant redacted logs.
Step 5: Scan and review
Search for all credential header names, token patterns, emails, names, deal values, transcript text, and signed URLs; require human review before sharing.
Step 6: Seal and expire
Hash the bundle, encrypt it, record recipients and expiry, and delete working copies according to incident policy.
Authentication
Never collect values for apikey, partnerkey, X-Api-Key, or X-Api-Password. If a credential may have entered any artifact, stop distribution and rotate it before continuing.
Tool Discipline
Use Read and Grep to inspect configuration, provider contracts, fixtures, logs, schemas, and existing tests before proposing a change. Use Write or Edit only for the approved plan, implementation, test, or redacted receipt; do not issue, rotate, revoke, create, update, cancel, delete, export, ingest, or publish provider data without explicit operator approval.
Show full SKILL.md (146 more words)Show less
Output
- Redacted manifest and evidence inventory
- Job or cursor timeline plus schema and reconciliation summaries
- Bundle hash, reviewer, recipients, expiry, and deletion receipt
Return the exact surface, environment, resource or job identifiers, contract fingerprint, evidence, unresolved risks, and final decision without exposing credentials or sensitive customer data.
Examples
A stuck forecast incident bundle includes the job ID, STARTED timeline, provider error ID, contract hash, scheduler version, and empty-result schema—but no token, forecast rows, or user email addresses.
Error Handling
| Failure | Response |
|---|---|
| Scanner finds a credential or sensitive value | Quarantine the bundle, rotate if necessary, redact, and restart review. |
| Evidence lacks a job ID or cursor | Correlate through request fingerprint and timestamps; state the uncertainty explicitly. |
| Bundle is too large | Replace payloads with hashes, schemas, counts, and the smallest approved redacted sample. |
Resources
© 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/clari-debug-bundle of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Clari 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 |
|---|---|---|---|---|---|---|
| Clari Debug Bundle this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1k | Automated safety check: Pass | MIT | |
| Debugasgeirtj/system_prompts_leaks | 69k | — | ~439 | Automated safety check: Pass | CC0-1.0 | |
| Runtime Debugvercel/next.js | 143k | 1 repos | ~618 | Automated safety check: Pass | MIT | |
| Openclaw Debuggingopenclaw/openclaw | 392k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| DebuggingJetBrains/intellij-community | 21k | — | ~422 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Runtime Debug
vercel/next.js
Debug and verification workflow for runtime-bundle and module-resolution regressions.
Openclaw Debugging
openclaw/openclaw
Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
- Official
Debugging
JetBrains/intellij-community
Debug IntelliJ IDE failures with repository-specific techniques.
Debugging Toolkit
sickn33/agentic-awesome-skills
A skill your agent uses when working with debugging toolkit smart debug (Alias for debugging-toolkit-smart-debug)
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.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Questions about Clari Debug Bundle
What does Clari Debug Bundle do?
Analyze a Clari incident and collect a minimal support bundle with job timelines, contract fingerprints, and secret-safe evidence. Clari Debug Bundle is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze a Clari incident and collect a minimal support bundle with job timelines, contract fingerprints, and secret-safe evidence.
When should I use Clari Debug Bundle?
Clari Debug Bundle fits situations like: escalating a provider; pipeline failure; with: collect Clari diagnostics; build a Clari support bundle.
How do I install Clari Debug Bundle in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clari-debug-bundle -a claude-code`. Or copy the skill folder (skills/.curated/clari-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clari-debug-bundle in your project. Claude Code loads it when a task matches its description.
How do I install Clari Debug Bundle in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clari-debug-bundle -a codex`. Or copy the skill folder (skills/.curated/clari-debug-bundle in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clari-debug-bundle in your project. Codex loads it when a task matches its description.
Can I use Clari 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 clari-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/clari-debug-bundle, .gemini/skills/clari-debug-bundle, .github/skills/clari-debug-bundle and .opencode/skills/clari-debug-bundle in your project.
What does Clari Debug Bundle need to run?
SKILL.md names no scripts, command-line tools or credentials: Clari Debug Bundle is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit. Compatibility (from SKILL.md): Requires an incident identifier, authorized time window, redaction policy, and an encrypted evidence destination..
Does Clari Debug Bundle access the network?
SKILL.md names 3 domains. As links in the text: developer.clari.com, api-doc.copilot.clari.com and clari.statuspage.io. This is read from the text; nothing was executed.
Is Clari 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 Clari Debug Bundle use?
Clari 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 Clari Debug Bundle use?
About 1k tokens (SKILL.md is roughly 4.2k 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 486 tokens, read only when the agent opens those files.
What are the alternatives to Clari Debug Bundle?
Skills that share tags, products or a category with Clari Debug Bundle: Debug (asgeirtj/system_prompts_leaks, 69k stars), Runtime Debug (vercel/next.js, 143k stars), Openclaw Debugging (openclaw/openclaw, 392k stars) and Debugging Executions (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clari Debug Bundle?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 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.