CtrlK
BlogDocsLog inGet started
Tessl Logo

gamma-install-auth

Set up Gamma API v1.0 authentication and first request. Use when configuring API keys, setting up X-API-KEY header, or initializing Gamma REST API access in a project. Trigger: "install gamma", "setup gamma API", "gamma auth", "gamma API key", "configure gamma".

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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 with executable code, exact endpoints, and a clear sequenced setup workflow including a verification checkpoint. Its main weakness is mild redundancy across the three verification examples, which keeps conciseness at level 2.

Suggestions

Consolidate the three verification paths: keep one inline curl check and move the full Node and Python clients into a single representative example or a separate reference, reducing token overlap.

If the full client wrappers grow further, split them into a references/ file linked from a Quick start section to preserve a lean overview.

DimensionReasoningScore

Conciseness

The body is lean with no concept re-explanation, but provides three overlapping verification paths (curl in Step 3 plus full Node and Python clients in Steps 4 and 5) that could be tightened. It is not level 3 because of that redundancy, and not level 1 because nothing is padded or verbose.

2 / 3

Actionability

Everything is copy-paste ready: exact curl commands, real API URLs, complete TypeScript and Python wrappers, and an HTTP-status-to-fix error table. It is not level 2 because there is no pseudocode or missing key detail.

3 / 3

Workflow Clarity

Steps 1 through 5 are clearly sequenced with an explicit validation checkpoint ("200 = authenticated, 401 = invalid key"). This is a non-destructive single-purpose setup where the verification is unambiguous, so it meets the level-3 bar; it is not level 2 because the checkpoint is explicit rather than implicit.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is a self-contained single file with well-organized sections (Overview, Prerequisites, Steps, Security, Error Handling, Notes, Resources) and one-level outward links to docs and a sibling skill. It is not level 2 because references are clearly signaled and not nested.

3 / 3

Total

11

/

12

Passed

Description

90%Weight 40%Scale 1-3

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: it states a concrete purpose, gives an explicit Use-when clause, and lists natural trigger phrases scoped to the Gamma API, making it clear and unlikely to conflict. Its only weakness is that the listed actions are all facets of a single auth-setup task rather than a broad set of distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("Set up Gamma API v1.0 authentication and first request", "configuring API keys, setting up X-API-KEY header"). The actions are variations of one auth-setup task rather than multiple distinct operations, so it sits at level 2 rather than 3.

2 / 3

Completeness

It answers both what ("Set up Gamma API v1.0 authentication and first request") and when ("Use when configuring API keys, setting up X-API-KEY header, or initializing Gamma REST API access") with explicit triggers. Clearly above level 2, which requires the when to be missing or only implied.

3 / 3

Trigger Term Quality

An explicit Trigger: clause lists natural phrases a user would say ("install gamma", "setup gamma API", "gamma auth", "gamma API key", "configure gamma"), giving good coverage of natural terms. It is not level 2 because it does not miss common variations.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to the Gamma product and its X-API-KEY auth flow with product-named triggers, making it unlikely to fire for unrelated skills. Not level 2 because the niche is distinct rather than overlapping.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.