ideogram-install-auth
Install and configure Ideogram SDK/CLI authentication. Use when setting up a new Ideogram integration, configuring API keys, or initializing Ideogram in your project. Trigger with phrases like "install ideogram", "setup ideogram", "ideogram auth", "configure ideogram API key".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-install-auth83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger terms and completeness. It clearly defines when to use the skill and includes natural user phrases. The main weakness is that the capability description could be more specific about the concrete actions performed during setup.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram SDK/CLI) and some actions (install, configure, authentication), but doesn't list comprehensive specific actions like 'generate API key file', 'validate credentials', or 'set environment variables'. | 2 / 3 |
Completeness | Clearly answers both what (install and configure Ideogram SDK/CLI authentication) and when (setting up new integration, configuring API keys, initializing). Includes explicit 'Use when' clause and 'Trigger with phrases' section. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'install ideogram', 'setup ideogram', 'ideogram auth', 'configure ideogram API key'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on Ideogram SDK/CLI setup and authentication. The explicit product name 'Ideogram' and specific actions like 'auth' and 'API key' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured installation skill with good organization and appropriate conciseness. The main weakness is the incomplete verification step (Step 3), which undermines the workflow by leaving Claude without concrete code to confirm successful setup. The error handling table is a nice addition but doesn't compensate for the missing verification code.
Suggestions
Complete Step 3 with actual executable verification code for both TypeScript and Python (e.g., a simple API call that confirms authentication works)
Add explicit success/failure indicators for the verification step so Claude knows what output confirms successful setup
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining what SDKs or API keys are. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Most code is executable and copy-paste ready, but Step 3 'Verify Connection' contains only a placeholder comment '// Test connection code here' instead of actual verification code, which is a significant gap. | 2 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but the verification step is incomplete. There's no explicit validation checkpoint or feedback loop for confirming the connection actually works before proceeding. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, appropriate length for a setup skill, and good navigation to external resources and next steps without unnecessary nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.