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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable, copy-paste-ready code and clear redaction guidance, but it is monolithic and somewhat redundant. Splitting the large scripts into bundle files and adding explicit validation checkpoints would lift the weaker dimensions.

Suggestions

Move the ~60-line bundle script and the TypeScript logging wrapper into a scripts/ directory and reference them from the body to improve progressive disclosure and reduce inline bulk.

Add an explicit validation checkpoint after Step 1 (e.g. verify the tarball exists and contains summary.txt, api-response-sample.json, env-redacted.txt before considering the bundle complete) to strengthen workflow clarity.

De-duplicate the 'Current State' version-gathering !-blocks and the Step 1/Step 2 overlapping API connectivity tests, or explicitly state how the quick one-liner differs from the full bundle's test.

Dimension	Reasoning	Score
Conciseness	The body is code-forward with no concept-explanation fluff, but the 'Current State' !-blocks duplicate what the Step 1 script gathers, Step 2's API test overlaps Step 1's connectivity test, and the Error Handling table restates script output categories, so it could be tightened.	2 / 3
Actionability	It provides a fully executable bash bundle script, concrete curl one-liners, and a copy-paste-ready TypeScript logging wrapper with specific endpoints and payloads.	3 / 3
Workflow Clarity	Steps 1-3 are clearly sequenced and the script uses 'set -euo pipefail' with an output echo, but there is no explicit validate->fix->retry feedback loop and checkpoints remain implicit rather than stated.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is monolithic with a ~60-line bash script and a TypeScript wrapper inline that could be split into scripts/ files; at over 50 lines the simple-skill exemption does not apply.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it explicitly covers what and when, uses natural trigger phrases, and is clearly scoped to Ideogram diagnostics. Its only weakness is that the named actions are variations of a single 'collect debug evidence' operation rather than multiple distinct concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain and a few actions ('Collect Ideogram debug evidence', 'preparing support tickets', 'collecting diagnostic information'), but these are variants of one collection action rather than the multiple distinct concrete operations the top anchor requires.	2 / 3
Completeness	It explicitly states what the skill does ('Collect Ideogram debug evidence for support tickets and troubleshooting') and when to use it ('Use when encountering persistent issues...'), plus explicit trigger phrases, satisfying both what and when.	3 / 3
Trigger Term Quality	Trigger phrases like 'ideogram debug', 'ideogram support bundle', 'collect ideogram logs', and 'ideogram diagnostic' are natural terms a user would actually say, with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear, Ideogram-specific niche with distinct trigger phrases, making it unlikely to fire for or conflict with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.