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

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

80%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 lean, executable, and well-organized with concrete code for every step and a startup validation checkpoint. Its main weaknesses are the absence of per-step validation between the destructive secret/deploy steps and a monolithic single-file layout that bundles content a progressive structure would split out.

Suggestions

Add explicit validation/feedback checkpoints between Step 3 (secret creation) and Step 4 (deploy) — e.g., verify each secret was created before proceeding — so destructive operations are guarded per-step rather than only at startup.

Move the platform-specific secret-management commands (AWS/GCP/GitHub) or the full TypeScript config into reference files under ./references/ and link to them from SKILL.md, keeping the main body a concise overview.

Tighten or relocate the Resources and Next Steps sections so the body stays focused on the actionable workflow and the ideogram-deploy-integration pointer is clearly framed as a one-level-deep reference.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and assumes competence — it never explains what Ideogram or environment concepts are — and every section (config, env files, secret commands, CI yaml, validation) earns its place. It sits just above the 2 anchor by avoiding all concept padding.	3 / 3
Actionability	Provides fully executable TypeScript config, copy-paste bash (gh secret set, aws secretsmanager create-secret, gcloud secrets create), a complete GitHub Actions workflow, and a zod startup validation block — concrete and ready to run.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and Step 5 gives an explicit validate-on-error checkpoint, but the destructive secret-creation (Step 3) and deploy (Step 4) steps lack per-step validation/feedback loops, so it caps at 2 rather than 3.	2 / 3
Progressive Disclosure	The single SKILL.md is well-sectioned and its only reference (Next Steps → ideogram-deploy-integration) is one level deep, but substantial inline blocks (full TS config, per-platform secret commands) that could be split into separate files keep it from the 3 anchor.	2 / 3
	Total	10 / 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 third-person, concrete, and complete — it states what the skill does, when to use it, and supplies natural trigger phrases. It is a strong, low-conflict description that would activate reliably.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Configure Ideogram across development, staging, and production environments", "setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Ideogram configurations" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Configure Ideogram across development, staging, and production environments") and when ("Use when setting up multi-environment deployments, configuring per-environment keys"), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram multi-env" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The "ideogram" qualifier plus multi-environment framing carves a clear niche with distinct triggers, making overlap with other skills unlikely.	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-multi-env-setup/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.