CtrlK
BlogDocsLog inGet started
Tessl Logo

ideogram-deploy-integration

Deploy Ideogram integrations to Vercel, Cloud Run, and Docker platforms. Use when deploying Ideogram-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy ideogram", "ideogram Vercel", "ideogram production deploy", "ideogram Cloud Run", "ideogram Docker".

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A strong, actionable deployment guide with complete executable code across three platforms. Its main gaps are missing validation/verification checkpoints in the deploy workflow and inline-heavy content that would benefit from splitting into reference files.

Suggestions

Add explicit validation checkpoints to the deployment steps — e.g. after `gcloud run deploy`, run a curl/health check against the service URL and only report success once it returns 200.

Move the full Next.js route handler, Dockerfile, and docker-compose snippets into files under references/ and link to them, keeping SKILL.md as a lean overview.

Add a brief verification block (e.g. hit the health endpoint and confirm a test generate request returns a persisted CDN URL) so Claude can confirm the deploy worked before finishing.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code, but the full inline Next.js route handler and complete Dockerfile/compose blocks push length higher than the lean anchor; some of this material could live in reference files.

2 / 3

Actionability

Provides complete, executable TypeScript, Dockerfile, docker-compose, gcloud, and vercel snippets that are copy-paste ready, satisfying the fully-executable anchor.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1–5) but there are no validation/verification checkpoints — e.g. no test or confirm-deploy step after the Cloud Run deploy — and the skill involves production deployment, so the missing feedback loop caps this at 2.

2 / 3

Progressive Disclosure

Sections are well organized, but no bundle/reference files exist and the large inline code blocks that could be split out (full route handler, Dockerfile, compose) are kept in SKILL.md rather than referenced one level deep.

2 / 3

Total

9

/

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.

A well-constructed description that states concrete capabilities, provides explicit use-when guidance, and lists natural trigger phrases with minimal padding. Its only minor weakness is the multi-line wrapped formatting, but content quality is strong.

DimensionReasoningScore

Specificity

Lists multiple concrete deploy actions across three platforms — "Deploy Ideogram integrations to Vercel, Cloud Run, and Docker platforms" and "configuring platform-specific secrets, or setting up deployment pipelines" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what it does (deploy Ideogram integrations, configure secrets, set up pipelines) and when to use it via a clear "Use when..." clause plus an explicit trigger list.

3 / 3

Trigger Term Quality

Includes a broad set of natural user phrases — "deploy ideogram", "ideogram Vercel", "ideogram production deploy", "ideogram Cloud Run", "ideogram Docker" — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The narrow Ideogram-specific deploy niche with distinctive named triggers makes 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.