gamma-security-basics

Implement security best practices for Gamma integration. Use when securing API keys, implementing access controls, or auditing Gamma security configuration. Trigger with phrases like "gamma security", "gamma API key security", "gamma secure", "gamma credentials", "gamma access control".

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/gamma-pack/skills/gamma-security-basics/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The body is an actionable, reasonably lean set of security patterns with real code and a useful checklist. Its main weaknesses are missing validation/verification feedback loops around the destructive key-rotation workflow and no progressive disclosure into supporting reference files.

Suggestions

Add an explicit validation/verification checkpoint to the key rotation workflow (e.g. 'after swapping PRIMARY, verify requests succeed before revoking the old key') so the destructive step has a validate-fix-retry loop.

Replace the comment-only rotation pseudocode with an executable script or concrete verification command to lift actionability on that step.

Move the full audit-logging and request-signing patterns into a separate reference file linked from SKILL.md so the overview stays lean and progresses to detail one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly lean code-with-checklist structure that assumes competence, with only minor padding like the 'NEVER do this' contrast and commented rotation steps; no large over-explanation of concepts Claude already knows.	4 / 5
Actionability	Each step ships concrete, mostly copy-pasteable TypeScript (key loading, HMAC signing, scoped clients, audit interceptors), with minor gaps: the rotation step is comment-only pseudocode and several steps hedge with 'if supported'.	4 / 5
Workflow Clarity	Steps 1-5 are sequenced and supported by a checklist and error-handling table, but key rotation (a destructive/irreversible operation) has no validate-then-fix feedback loop, capping this dimension per the rubric's destructive-operation rule.	3 / 5
Progressive Disclosure	Sections are organized but all content is inlined into a single SKILL.md with no bundle files or one-level-deep references, so content that could live in separate files (e.g. full audit/logging patterns) is kept inline.	3 / 5
	Total	14 / 20 Passed

Description

82%Weight 40%Scale 1-5

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 complete and distinctive, clearly stating what the skill does and when to use it with concrete Gamma-specific trigger phrases. Specificity is the weakest area, resting on a generic 'security best practices' framing rather than enumerating comprehensive concrete actions.

Dimension	Reasoning	Score
Specificity	Names the Gamma security domain and 2-3 concrete actions ('securing API keys, implementing access controls, or auditing Gamma security configuration'), but coverage is not comprehensive and 'security best practices' is somewhat generic.	3 / 5
Completeness	Explicitly answers both what ('Implement security best practices for Gamma integration') and when ('Use when securing API keys...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Lists several natural trigger phrases ('gamma security', 'gamma credentials', 'gamma access control') that users would plausibly say, though they read as deliberately stuffed and miss a few synonyms.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to Gamma security, a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 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
Path: plugins/saas-packs/gamma-pack/skills/gamma-security-basics/SKILL.md
Commit: 8585d6d

Reviewed: 13 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.