Name: tinfoil-security
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

tinfoil-security

Tinfoil Security integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tinfoil Security data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tinfoil-security/SKILL.md

Quality

Content

75%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 a strong, actionable CLI integration guide with executable commands and good workflow checkpoints, weakened only by a redundant intro paragraph, a broken 'Step 2' cross-reference, and some over-inline reference material.

Suggestions

Trim or remove the opening marketing paragraph about Tinfoil's purpose; assume Claude knows what the product is.

Fix the dangling 'skip to Step 2' reference and label the connection section '1a' to match '1b', or restructure without loose step references.

De-duplicate the action-list command, which appears nearly verbatim in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command documentation, but the opening marketing paragraph ('helps SaaS companies find and fix security vulnerabilities...') explains context Claude doesn't need, and the action-list command is repeated across sections.	3 / 5
Actionability	Copy-paste ready commands cover install, login, connection ensure, polling, action list/run, and proxy requests, plus a thorough flag table for the proxy.	5 / 5
Workflow Clarity	A clear install→auth→connect→poll→run sequence with state-based validation and feedback loops exists, but the 'skip to Step 2' reference is dangling and there is no '1a' counterpart to '1b'.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested external references, though some inline schema-like detail (clientAction fields, the flag table) could arguably live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

57%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 answers both what and when with an explicit trigger clause, but the capability wording ('manage data, records, automate workflows') is generic and undersells Tinfoil's concrete scanning and vulnerability features.

Suggestions

Replace generic verbs with Tinfoil-specific capabilities, e.g. 'Run vulnerability scans, retrieve scan results and findings, and manage users.'

Expand the trigger clause with natural task phrases users would say, e.g. 'Use when the user wants to run scans, review findings, or manage Tinfoil Security data.'

Avoid first/second person and keep the concrete actions prominent so the skill triggers on the right requests.

Dimension	Reasoning	Score
Specificity	It names the domain ('Tinfoil Security integration') but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities like scanning or vulnerability findings.	2 / 5
Completeness	Both a 'what' (integration managing data, records, workflows) and an explicit 'when' ('Use when the user wants to interact with Tinfoil Security data') are present, though the when could be more specific.	4 / 5
Trigger Term Quality	The 'Use when...' clause references the product name 'Tinfoil Security data', a relevant natural keyword, but no synonyms, variations, or specific task terms are present.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Tinfoil Security' gives it a clear niche with minor overlap risk, though the generic action phrasing could loosely overlap with other integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/tinfoil-security/SKILL.md
Commit: f484c82

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