gamma-hello-world

Generate your first Gamma presentation via the API. Use when learning the generate-poll-retrieve workflow, testing API connectivity, or creating a minimal example. Trigger: "gamma hello world", "gamma quick start", "first gamma presentation", "gamma example", "gamma test".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and clearly sequenced, with executable examples in three languages, a concrete expected-output shape, and helpful error/parameter tables. The main token-efficiency concern is the triple-language redundancy for a minimal-example skill.

Suggestions

Keep one canonical example (e.g. curl) inline and move the Node.js and Python variants into a referenced file or a collapsible appendix to reduce redundancy for a hello-world skill.

Add a brief note on handling the 401/422 cases inside the code examples so the error-handling table and the code stay in sync.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but it provides three full implementations (curl, Node.js/TypeScript, Python) of the same generate-poll-retrieve workflow, which is redundant for a hello-world skill and could be tightened, matching the level-2 anchor.	2 / 3
Actionability	All three examples are fully executable, copy-paste-ready code with real endpoints, auth headers, and jq/JSON parsing, plus concrete expected output and parameter tables, matching the level-3 anchor.	3 / 3
Workflow Clarity	The generate-poll-retrieve flow is explicitly numbered (POST -> poll every 5s until completed/failed -> retrieve) with a status-checkpoint feedback loop and an error-recovery table; this is not a destructive/batch operation so no validation cap applies, matching level 3.	3 / 3
Progressive Disclosure	No bundle files exist, and the content is organized into clear, navigable sections with one-level-deep external resource links and a Next Steps pointer; a self-contained hello-world skill needs no file splits, so the well-organized sections satisfy level 3 per the simple-skills note.	3 / 3
	Total	11 / 12 Passed

Description

80%

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 is strong on completeness, triggers, and distinctiveness, clearly conveying both what the skill does and when to use it with natural trigger phrases. Its only weakness is the second-person phrasing ("your first Gamma presentation"), which the rubric penalizes on specificity.

Suggestions

Rewrite the description in third person to match the rubric's good examples, e.g. "Generates a first Gamma presentation via the API." instead of "Generate your first Gamma presentation via the API."

Add one or two more concrete capability verbs beyond "generate" (e.g. "submit, poll, and retrieve") to lift specificity without adding fluff.

Dimension	Reasoning	Score
Specificity	Names the domain and a single concrete action ("Generate your first Gamma presentation via the API"), but the remaining clauses are use-cases rather than multiple distinct capabilities, matching the level-2 anchor. The second-person voice ("your first Gamma presentation") triggers the rubric's -1 specificity penalty, lowering it to 1.	1 / 3
Completeness	It states what the skill does (generate a first Gamma presentation via the API) and explicitly when to use it ("Use when learning the generate-poll-retrieve workflow, testing API connectivity, or creating a minimal example") plus a Trigger line, satisfying both halves at level 3.	3 / 3
Trigger Term Quality	The explicit "Trigger:" line lists five natural phrases ("gamma hello world", "gamma quick start", "first gamma presentation", "gamma example", "gamma test") that users would plausibly say, matching the level-3 anchor for good coverage.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (Gamma API, minimal/first presentation) with Gamma-specific triggers, making it unlikely to fire for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.