ideogram-debug-bundle
Collect Ideogram debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Ideogram problems. Trigger with phrases like "ideogram debug", "ideogram support bundle", "collect ideogram logs", "ideogram diagnostic".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-debug-bundle83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger term coverage and clear when/what guidance. The main weakness is the lack of specific concrete actions - it describes the general purpose but not the specific capabilities like what types of evidence are collected or what diagnostic steps are performed.
Suggestions
Add specific concrete actions such as 'capture API responses', 'export generation logs', 'gather configuration settings', or 'screenshot error states' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram debug) and general actions (collect evidence, troubleshooting, preparing support tickets), but lacks specific concrete actions like 'capture screenshots', 'export logs', or 'gather configuration files'. | 2 / 3 |
Completeness | Clearly answers both what (collect debug evidence for support tickets and troubleshooting) and when (encountering persistent issues, preparing support tickets, collecting diagnostic information) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'ideogram debug', 'ideogram support bundle', 'collect ideogram logs', 'ideogram diagnostic'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Ideogram-specific debugging and support. The explicit 'ideogram' prefix on all triggers makes it highly unlikely to conflict with general debugging or other tool-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable bash scripts for creating debug bundles. The main weaknesses are some redundant content (prerequisites, duplicated info in error handling table) and missing validation steps to verify bundle integrity and sensitive data redaction before submission.
Suggestions
Add a validation step after Step 4 to verify the bundle contents and confirm no unredacted secrets remain (e.g., grep for common secret patterns)
Remove the prerequisites section - Claude knows SDK installation is required and can infer permissions needed
Consolidate the error handling table with the script comments to avoid duplication
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the prerequisites section (Claude knows SDK needs to be installed) and the error handling table which duplicates information already shown in the script. | 2 / 3 |
Actionability | Provides fully executable bash scripts that are copy-paste ready, with specific commands for each step of the debug bundle creation process. The code is complete and functional. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. There's no verification step to confirm the bundle was created correctly or that sensitive data was properly redacted before submission. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate length for a single skill file, and includes relevant cross-references to related resources (support portal, status page, rate-limits skill) without unnecessary nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.