gamma-reference-architecture
Reference architecture for enterprise Gamma integrations. Use when designing systems, planning integrations, or implementing best-practice Gamma architectures. Trigger with phrases like "gamma architecture", "gamma design", "gamma system design", "gamma integration pattern", "gamma enterprise".
34
31%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-reference-architecture/SKILL.mdQuality
Discovery
40%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 suffers from a lack of specificity about what the skill actually does—it reads like a buzzword-heavy enterprise blurb rather than a concrete capability description. While it commendably includes explicit trigger phrases and a 'Use when' clause, the absence of concrete actions (what does it produce? what formats? what specific integration patterns?) makes it difficult for Claude to confidently select this skill or for users to understand its value.
Suggestions
Replace vague language with specific concrete actions, e.g., 'Generates architecture diagrams, API integration blueprints, and data flow specifications for Gamma platform integrations'.
Define what 'Gamma' is briefly (e.g., a specific platform, API, or framework) to reduce ambiguity and improve distinctiveness against other architecture/integration skills.
Add natural user language variations to trigger terms, such as 'connect to Gamma', 'Gamma setup', 'Gamma API', 'Gamma configuration' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'reference architecture', 'designing systems', 'planning integrations', and 'best-practice architectures' without listing any concrete actions. There are no specific capabilities described—no verbs like 'generate diagrams', 'create API endpoints', or 'configure middleware'. | 1 / 3 |
Completeness | The description has a 'Use when...' clause and trigger phrases, addressing the 'when' dimension. However, the 'what' dimension is extremely weak—'reference architecture for enterprise Gamma integrations' is too vague to understand what the skill actually does or produces. | 2 / 3 |
Trigger Term Quality | The description explicitly lists trigger phrases like 'gamma architecture', 'gamma design', 'gamma system design', 'gamma integration pattern', 'gamma enterprise'. These are somewhat relevant but are all variations of the same pattern and lack natural user language variations (e.g., 'how to connect Gamma', 'Gamma setup', 'Gamma API'). | 2 / 3 |
Distinctiveness Conflict Risk | The term 'Gamma' provides some distinctiveness as a named product/platform, but the rest of the description ('designing systems', 'planning integrations', 'architectures') is generic enough to overlap with any system design or integration planning skill. Without knowing what Gamma is or what specific outputs this skill produces, conflict risk remains moderate. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a verbose, largely generic architecture reference that consumes excessive tokens on ASCII diagrams and concepts Claude already understands. It lacks clear workflows, validation steps, and decision-making guidance for when to use each pattern. The code examples provide some actionability but reference an unverifiable SDK and contain a syntax error.
Suggestions
Replace large ASCII diagrams with brief textual descriptions of each pattern's components and data flow, saving significant token budget.
Add a clear decision workflow: 'If X, use Pattern 1; if Y, use Pattern 2; if Z, use Pattern 3' with specific criteria rather than vague use-case labels.
Remove the prerequisites section entirely—Claude already knows about microservices, cloud architecture, and event-driven systems.
Add explicit implementation steps with validation checkpoints (e.g., 'Verify API connectivity before proceeding to service layer setup') rather than just showing disconnected code snippets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with massive ASCII diagrams that consume enormous token budgets. The prerequisites section explains concepts Claude already knows (microservices, cloud architecture, event-driven systems). Much of the content is generic architecture knowledge not specific to 'Gamma' and could be drastically condensed. | 1 / 3 |
Actionability | The TypeScript code examples are relatively concrete and near-executable, but they reference a fictional '@gamma/sdk' package with no verifiable API. The architecture diagrams describe patterns abstractly rather than providing specific, actionable implementation steps. There's a syntax error (Python comment `#` in TypeScript code). | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for implementing any of the patterns. The skill presents three architecture patterns and code snippets but never guides the user through a step-by-step process of designing or implementing an integration. No validation checkpoints or decision criteria for choosing between patterns are provided. | 1 / 3 |
Progressive Disclosure | The content has some structure with sections and a reference to 'gamma-multi-env-setup' for next steps, but the massive inline ASCII diagrams and full code examples make it a near-monolithic wall of content. No bundle files exist to offload detailed content, and the inline material could benefit from being split into separate reference files. | 2 / 3 |
Total | 6 / 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
c2ae302
- 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.