ideogram-reference-architecture
Implement Ideogram reference architecture with best-practice project layout. Use when designing new Ideogram integrations, reviewing project structure, or establishing architecture standards for Ideogram applications. Trigger with phrases like "ideogram architecture", "ideogram best practices", "ideogram project structure", "how to organize ideogram", "ideogram layout".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-reference-architecture78
Quality
70%
Does it follow best practices?
Impact
98%
2.33xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/ideogram-pack/skills/ideogram-reference-architecture/SKILL.mdDiscovery
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 description has strong completeness with explicit 'Use when' and 'Trigger with' clauses, and excellent distinctiveness due to its Ideogram-specific focus. The main weakness is the lack of concrete, specific actions - it describes the general purpose but doesn't enumerate what specific tasks it performs (e.g., creating directories, configuring files, setting up patterns).
Suggestions
Add specific concrete actions like 'Creates folder structure, configures API clients, sets up error handling patterns, establishes module organization'
Consider adding file types or artifacts produced (e.g., 'generates config files, directory templates, boilerplate code')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram) and mentions 'reference architecture' and 'best-practice project layout', but lacks concrete actions like 'create folder structure', 'configure modules', or 'set up API clients'. | 2 / 3 |
Completeness | Clearly answers both what (implement reference architecture with best-practice layout) and when (designing integrations, reviewing structure, establishing standards) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'ideogram architecture', 'ideogram best practices', 'ideogram project structure', 'how to organize ideogram', 'ideogram layout' - good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Ideogram architecture and project structure - unlikely to conflict with other skills due to the niche domain focus and explicit Ideogram-specific trigger terms. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable reference architecture with useful diagrams and code snippets, but suffers from incomplete implementations and vague instructions. The content mixes high-level overview with detailed code without clear separation, and lacks validation checkpoints for the multi-step setup process.
Suggestions
Complete the code examples (e.g., implement wrapIdeogramError, define IdeogramClient import) to make them copy-paste ready
Add validation steps after each instruction (e.g., 'Verify: run `tsc --noEmit` to check types compile')
Move detailed code implementations to a separate REFERENCE.md and keep SKILL.md as a concise overview with the project structure and quick setup
Remove the Prerequisites section - Claude already understands layered architecture and TypeScript
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'Prerequisites' listing things Claude already knows (layered architecture, TypeScript setup). The structure diagrams and code examples are useful but could be tighter. | 2 / 3 |
Actionability | Provides concrete code examples and a bash setup script, but many code snippets are incomplete (e.g., wrapIdeogramError has no implementation, IdeogramClient is undefined). The 'Instructions' section is vague ('Create the singleton client with caching') rather than executable. | 2 / 3 |
Workflow Clarity | Steps are listed (Step 1-4) but lack validation checkpoints. No verification that the structure is correct, no feedback loops for common errors, and no explicit 'validate your setup' step before proceeding. | 2 / 3 |
Progressive Disclosure | References external docs and a flagship skill at the end, but the main content is a monolithic wall mixing project structure, code examples, diagrams, and instructions. Could benefit from splitting detailed implementations into separate reference files. | 2 / 3 |
Total | 8 / 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.