ideogram-local-dev-loop

Configure Ideogram local development with mock responses and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Ideogram. Trigger with phrases like "ideogram dev setup", "ideogram local development", "ideogram dev environment", "develop with ideogram", "ideogram testing".

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/ideogram-pack/skills/ideogram-local-dev-loop/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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 complete, executable code and a clear step sequence. It loses points on token efficiency, missing validation checkpoints, and the absence of progressive disclosure — the full implementation lives entirely inline rather than being split into reference files.

Suggestions

Add an explicit validation checkpoint between setup and use, e.g. a step 'Run `npm test` to confirm the client, mock server, and fetch mocking work before iterating.'

Move the larger code blocks (typed client, mock-server, full vitest suite) into reference files under references/ and link to them from SKILL.md so the overview stays lean and supports progressive disclosure.

Trim inline content that does not earn its place in the overview file — keep SKILL.md as a quick-start pointing to the detailed implementation, reducing the single-file token load.

Dimension	Reasoning	Score
Conciseness	The prose assumes Claude's competence with no concept-explanation padding, but the entire implementation (types, client, mock-server, full vitest suite, scripts) is inlined in SKILL.md, making a single heavy file that could be tightened, matching 'mostly efficient but could be tightened'.	2 / 3
Actionability	The body provides complete, executable TypeScript (typed client, types, mock server, vitest tests), copy-paste npm install commands, and package.json scripts — fully copy-paste ready per the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps 1–7 are clearly sequenced, but there are no explicit validation checkpoints (e.g., a 'run npm test to verify the setup' step); only a reactive Error Handling table exists, matching 'steps listed but validation gaps; checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	No bundle files exist and all content is inlined in one well-sectioned but monolithic SKILL.md; the only cross-reference (ideogram-sdk-patterns) points to another skill rather than a bundle file, matching 'content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 states a concrete purpose, gives explicit 'Use when' guidance, and supplies natural trigger phrases with low conflict risk. The only soft spot is specificity, where the action list is narrow rather than a comprehensive set of concrete capabilities.

Dimension	Reasoning	Score
Specificity	"Configure Ideogram local development with mock responses and testing" names the domain plus a couple of adjuncts, but does not list multiple distinct concrete actions like the anchor-3 example, so it lands at 'names domain and some actions, but not comprehensive'.	2 / 3
Completeness	It explicitly answers both 'what' (Configure Ideogram local development with mock responses and testing) and 'when' (Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle, plus explicit trigger phrases), satisfying the 'clearly answers both what AND when' anchor.	3 / 3
Trigger Term Quality	The trigger phrases ("ideogram dev setup", "ideogram local development", "ideogram dev environment", "develop with ideogram", "ideogram testing") give good coverage of natural terms a user would actually say, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The skill occupies a clear niche (Ideogram local dev / mock / testing) with distinct, product-specific triggers, making it unlikely to fire for 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
Path: plugins/saas-packs/ideogram-pack/skills/ideogram-local-dev-loop/SKILL.md
Commit: 4c47e33

Reviewed: 3 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.