ideogram-install-auth
Install and configure Ideogram API 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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 solid, focused skill description for a narrow task. It clearly identifies the domain (Ideogram API authentication), provides explicit 'Use when' guidance, and includes natural trigger phrases. The main weakness is that the capability description could be slightly more specific about what concrete steps or outputs the skill produces beyond 'install and configure'.
Suggestions
Add more specific concrete actions, e.g., 'Generates API key configuration files, sets environment variables, validates authentication credentials' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram API) and some actions (install, configure, authentication), but doesn't list multiple concrete actions beyond setup-related tasks. It's somewhat specific but not comprehensive in detailing what steps or outputs are involved. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Ideogram API authentication) and 'when' (setting up a new integration, configuring API keys, initializing Ideogram) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would actually say: 'install ideogram', 'setup ideogram', 'ideogram auth', 'configure ideogram API key'. These are realistic phrases covering common variations of how a user would request this task. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Ideogram API setup and authentication. Unlikely to conflict with other skills due to the unique product name and narrow scope of installation/configuration. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear step-by-step workflow and executable code in two languages. Its main weakness is including substantial reference material (API endpoints table, billing details, error codes) inline that would be better served as linked reference files, making the skill longer than necessary for its core purpose of install and auth setup. The verification step with error handling is a strong point.
Suggestions
Move the API Base URLs table, billing model details, and error handling table to a separate REFERENCE.md file and link to it, keeping SKILL.md focused on the install/auth workflow.
Trim the overview paragraph — Claude doesn't need to be told what a REST API is or what Ideogram's capabilities are; just state the auth mechanism.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful reference tables (API URLs, error handling, billing) but some of this could be offloaded to separate reference files. The overview paragraph explaining what Ideogram is and what REST APIs do is mildly redundant for Claude. The verification code examples in two languages add bulk but are justified for actionability. | 2 / 3 |
Actionability | Provides fully executable code in both TypeScript and Python, specific bash commands for setup, exact navigation paths for obtaining API keys, and concrete verification steps. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step sequential process from obtaining the API key through verification. Step 4 includes explicit success/failure output handling, serving as a validation checkpoint. The workflow is well-ordered with each step building on the previous one. | 3 / 3 |
Progressive Disclosure | The skill has good structure with clear sections, but the API Base URLs table, billing model details, and error handling table are reference material that could be split into separate files. The content is somewhat monolithic for a setup/auth skill, though it does reference next steps and external docs. | 2 / 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 | |
- Commit
70e9fa4
- 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.