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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/ideogram-pack/skills/ideogram-debug-bundle/SKILL.mdQuality
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 solid skill description with excellent trigger terms and completeness. It clearly identifies when to use the skill and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more concrete — listing exactly what debug evidence is collected (logs, configs, screenshots, etc.) would improve specificity.
Suggestions
Add specific concrete actions like 'capture error logs, export configuration, screenshot UI state, bundle diagnostic artifacts' to improve specificity beyond the general 'collect debug evidence'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram debug evidence) and some actions (collect debug evidence, preparing support tickets, collecting diagnostic information), but doesn't list multiple specific concrete actions like 'capture logs, screenshot errors, export config, bundle artifacts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Ideogram 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: 'ideogram debug', 'ideogram support bundle', 'collect ideogram logs', 'ideogram diagnostic'. These are terms users would naturally say and cover good variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Ideogram debug evidence collection. The combination of 'Ideogram' + 'debug/diagnostic/support bundle' makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 debug bundle skill with complete, executable code and good security practices (redaction). Its main weaknesses are the lack of validation/interpretation guidance after collecting diagnostics (what do the results mean? when should you escalate?) and some verbosity in surrounding sections that don't add much beyond what the scripts already communicate. The inline length of the main script is substantial but justified given the single-purpose nature of the skill.
Suggestions
Add a brief interpretation guide after the bundle is created (e.g., 'If HTTP_STATUS is 401: key is invalid; if DNS fails: check network/proxy; if time_total > 10s: possible throttling') to close the diagnostic feedback loop.
Remove or condense the Error Handling table since it largely restates what's already visible in the script comments and output section.
Consider moving the full debug bundle script to a separate referenced file (e.g., `ideogram-debug-bundle.sh`) and keeping only the quick one-liner diagnostics inline for faster scanning.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements like the 'Current State' section with inline shell commands, the error handling table that partially duplicates what's already clear from the script, and the prerequisites section stating obvious things like 'curl and tar available'. The core script is well-written but the surrounding content could be tighter. | 2 / 3 |
Actionability | Fully executable bash scripts and TypeScript code are provided, ready to copy-paste and run. The debug bundle script is complete with proper error handling (set -euo pipefail), the one-liner diagnostics are immediately usable, and the TypeScript wrapper is a concrete, functional implementation. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (full bundle → quick diagnostics → logging wrapper), but there are no explicit validation checkpoints or feedback loops. After running the bundle script, there's no guidance on how to verify the bundle was created correctly, interpret results, or what to do if specific tests fail. For a diagnostic/troubleshooting skill, error interpretation guidance would strengthen the workflow. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the main script is quite long inline (~60 lines of bash). The sensitive data handling, error table, and output sections provide good organization. However, the single-file approach with everything inline makes it a wall of code; the detailed bundle script could potentially be referenced externally. The 'Next Steps' reference to ideogram-rate-limits is a good one-level-deep pointer. | 2 / 3 |
Total | 9 / 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 | |
- Commit
70e9fa4
- 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.