CtrlK
BlogDocsLog inGet started
Tessl Logo

ideogram-multi-env-setup

Configure Ideogram across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Ideogram configurations. Trigger with phrases like "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram multi-env".

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 with executable, copy-paste-ready code and a clear validated step sequence, but it is somewhat verbose (a redundant config table and a restating Output section) and monolithic where platform-specific detail could be offloaded to reference files.

Suggestions

Remove the Environment Strategy table or drop the duplicated model/speed/cache fields from one of the two places so those values appear only once (either the table or the config code).

Delete the Output section — it restates what the steps already produce — or fold its essential points into the Overview.

Move the per-platform secret-management scripts and the CI workflow into one-level reference files (e.g. references/secrets-by-platform.md, references/ci-workflow.yml), keeping SKILL.md an overview with clearly signaled links.

DimensionReasoningScore

Conciseness

Mostly efficient concrete code, but the Environment Strategy table duplicates model/speed/cache values already shown in the config code block, and the Output section restates what the steps produce rather than adding new information.

2 / 3

Actionability

Provides fully executable TypeScript config, bash secret-management commands, GitHub Actions YAML, and a zod validation snippet — copy-paste ready with specific values throughout.

3 / 3

Workflow Clarity

Five numbered steps form a clear sequence culminating in Step 5 startup validation (try/catch with process.exit), and the Error Handling table maps issues to fixes for recovery.

3 / 3

Progressive Disclosure

Sections are well-organized, but the ~200-line body is monolithic with substantial inline platform-specific content (three secret managers, CI YAML) that could be split into one-level reference files; no internal bundle references are used.

2 / 3

Total

10

/

12

Passed

Description

100%

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: concrete actions, an explicit 'Use when' trigger clause, natural trigger phrases, and a distinct Ideogram multi-environment niche in third-person voice. No specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Configure Ideogram across development, staging, and production environments', 'setting up multi-environment deployments, configuring per-environment keys', 'implementing environment-specific Ideogram configurations' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what it does ('Configure Ideogram across...') and when to use it ('Use when setting up multi-environment deployments...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Provides natural phrases a user would actually say — 'ideogram environments', 'ideogram staging', 'ideogram dev prod', 'ideogram environment setup', 'ideogram multi-env' — with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Ideogram-specific niche with 'ideogram'-prefixed triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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