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".
43
31%
Does it follow best practices?
Impact
Pending
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.
The description relies heavily on the term 'Gamma' for differentiation but fails to explain what Gamma is or what concrete actions the skill performs. The 'Use when' clause and trigger phrases are present but the lack of specific capabilities makes it difficult for Claude to confidently select this skill. The description reads more like a buzzword-laden summary than a functional guide for skill selection.
Suggestions
Replace vague language like 'reference architecture' and 'best-practice architectures' with specific concrete actions the skill performs (e.g., 'Generates integration diagrams, configures API endpoints, validates data flow patterns for Gamma platform').
Define what 'Gamma' is in the description so Claude can understand the domain (e.g., 'Gamma CRM platform' or 'Gamma messaging framework') and distinguish it from unrelated skills.
Add more natural trigger terms that users would actually say, such as specific file types, API names, or common tasks associated with Gamma integrations.
| 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', 'configure endpoints', or 'validate schemas'. | 1 / 3 |
Completeness | It has a 'Use when...' clause and explicit trigger phrases, addressing the 'when' question. However, the 'what' is extremely weak—'reference architecture for enterprise Gamma integrations' doesn't explain what the skill actually does in concrete terms, so the what/when balance is incomplete. | 2 / 3 |
Trigger Term Quality | It explicitly lists trigger phrases like 'gamma architecture', 'gamma design', 'gamma system design', 'gamma integration pattern', 'gamma enterprise'. These are somewhat relevant but feel artificially constructed rather than natural user language, and 'Gamma' itself is undefined, making it unclear what domain this covers. | 2 / 3 |
Distinctiveness Conflict Risk | The repeated use of 'Gamma' as a qualifier provides some distinctiveness, but terms like 'designing systems', 'planning integrations', and 'architecture' are very generic and could overlap with any system design or integration skill. Without knowing what 'Gamma' is, the niche is unclear. | 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 reference document that prioritizes visual presentation (large ASCII diagrams) over actionable guidance. It lacks workflow sequencing for implementing the described patterns, has no validation steps, and consumes excessive tokens with diagrams and prerequisites that don't add proportional value. The code examples provide some concreteness but reference an unverifiable SDK.
Suggestions
Replace large ASCII architecture diagrams with concise textual descriptions of component relationships (e.g., 'UI → API Server → Gamma Client → Gamma API') to dramatically reduce token usage.
Add a clear step-by-step workflow for implementing each pattern, including decision criteria for choosing between patterns and validation checkpoints (e.g., 'Verify API connectivity before proceeding').
Remove the prerequisites section entirely—Claude already understands microservices, cloud architecture, and event-driven systems.
Fix the syntax error in the TypeScript code (Python-style `#` comment on the cache TTL line) and ensure all code examples are copy-paste ready.
| 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). The diagrams could be replaced with brief textual descriptions. Multiple patterns are shown with extensive visual detail that adds little actionable value. | 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 structure but don't provide actionable implementation steps. The code has a syntax error (Python comment `#` in TypeScript) suggesting it's not fully vetted. | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for implementing any of the patterns. The skill presents patterns and code snippets but never guides the user through a step-by-step process of designing or building an integration. There are no validation checkpoints, decision points, or feedback loops for what is inherently a multi-step architectural process. | 1 / 3 |
Progressive Disclosure | The content has some structure with sections for patterns, implementation, and component responsibilities. However, the massive inline ASCII diagrams and full code examples make it a near-monolithic document. There are no bundle files to offload detailed content to, and the external references are generic links rather than structured skill references. | 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
3a2d27d
- 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.