ideogram-security-basics

Apply Ideogram security best practices for API key management and access control. Use when securing API keys, implementing key rotation, or auditing Ideogram security configuration. Trigger with phrases like "ideogram security", "ideogram secrets", "secure ideogram", "ideogram API key security", "ideogram key rotation".

Quality

96%

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

Quality

Content

92%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 body is highly actionable and concise with a well-sequenced, validated rotation workflow, but progressive disclosure is the weak point: everything lives inline and the only internal cross-reference ('ideogram-prod-checklist') points to a file that is not present in the bundle.

Suggestions

Resolve the dangling 'ideogram-prod-checklist' reference in '## Next Steps' — either add the file under references/ or remove the pointer, since progressive_disclosure penalizes references to missing material.

Move the longer reference material (e.g., the full rotation procedure and error-handling table) into a one-level-deep reference file with clearly signaled links from the overview, so SKILL.md stays a lean entry point.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with little explanatory padding; domain-specific notes like 'single Api-Key header… no OAuth scopes' earn their place. It is not the 2-anchor because it avoids generic concept explanation, though the '## Output' section lightly reiterates prior steps.	3 / 3
Actionability	Provides copy-paste-ready executable artifacts — .env/.gitignore blocks, a requireApiKey validator, rotation curl verification, a server-side proxy, a bash pre-commit hook, and a sanitizePrompt function — fully meeting the executable-and-complete anchor.	3 / 3
Workflow Clarity	Step 2's rotation procedure is a numbered sequence with an explicit verify-before-delete checkpoint ('4. Verify new key works', '6. Delete old key… after confirming zero traffic') over a destructive operation, avoiding the cap that missing validation would impose.	3 / 3
Progressive Disclosure	Content is well-sectioned but entirely inline with no bundle files to defer to, and 'Next Steps' references a non-existent 'ideogram-prod-checklist'. This fits the some-structure / inline-content-that-could-be-separate anchor rather than the well-signaled one-level-deep reference structure at 3.	2 / 3
	Total	11 / 12 Passed

Description

100%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 across all four dimensions: it states concrete actions, provides explicit 'Use when' guidance and natural trigger phrases, and occupies a distinct Ideogram-specific niche. The only weakness is formatting — the YAML folding introduces stray blank lines and dangling commas mid-sentence ('Use when securing API keys, implementing key rotation,, or auditing'), which hurts readability but not the scored content.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'API key management and access control', 'securing API keys', 'implementing key rotation', and 'auditing Ideogram security configuration' — matching the multi-action anchor rather than the vague single-domain anchor at 2.	3 / 3
Completeness	Answers both what ('Apply Ideogram security best practices for API key management and access control') and when ('Use when securing API keys, implementing key rotation, or auditing Ideogram security configuration') with explicit triggers, meeting the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Explicit 'Trigger with phrases like' block supplies natural terms users would say ('ideogram security', 'secure ideogram', 'ideogram API key security', 'ideogram key rotation'), giving good coverage beyond the partial-match anchor at 2.	3 / 3
Distinctiveness Conflict Risk	The Ideogram-specific scope and brand-named trigger phrases carve a clear niche unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 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-security-basics/SKILL.md
Commit: 4c47e33

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.