Name: footprint
Rating: 55.2 (1 reviews)
Author: membranedev

footprint

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/footprint/SKILL.md

Quality

Content

63%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 highly actionable with concrete CLI commands and a well-handled connection-readiness workflow, but it is dragged down by a large padded entity list and a lack of progressive disclosure into reference files. It is useful but inefficient.

Suggestions

Remove or collapse the ~95-item entity bullet list; rely on `membrane action list` discovery instead, or move it to a references file.

Add an explicit labeled 'Step 2' section so the 'skip to Step 2' cross-reference resolves.

Extract the proxy flag table and action schema details into a reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~95-item bullet list of entities (Project through Data Destruction) is a heavily padded data dump that adds little actionable value, fitting 'noticeably verbose; several padded sections'.	2 / 5
Actionability	It provides copy-paste-ready, executable commands for install, login, connection, action search/run, and proxy requests, with a flag table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-handle-repoll feedback loop, though 'Step 2' is referenced without a matching labeled section.	4 / 5
Progressive Disclosure	Section headers provide some structure, but no bundle files exist and the large entity list is inlined content that belongs in a separate reference or in CLI discovery, fitting 'content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

62%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 clearly identifies the Footprint product and provides an explicit use-when clause, but its action list is generic and its trigger vocabulary is narrow. It is solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with specific Footprint capabilities such as 'track carbon emissions, set sustainability goals, and generate compliance reports'.

Broaden trigger terms beyond 'interact with Footprint data' to natural phrases users would say, e.g. 'when the user mentions carbon footprint, emissions tracking, or sustainability reporting'.

Add concrete trigger cues (e.g. file types, report names, or metric terms) to strengthen the 'when' clause.

Dimension	Reasoning	Score
Specificity	Names the Footprint domain plus a few actions ('Manage data, records, and automate workflows'), but those actions are generic and not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Footprint data'), but the 'when' could be more specific with concrete trigger phrases, matching the 4 anchor.	4 / 5
Trigger Term Quality	The natural trigger phrase 'interact with Footprint data' is present, but coverage is thin with no synonyms or variations beyond the product name, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The named product 'Footprint' gives it a clear niche with distinct triggers, though the generic 'manage data, records, automate workflows' phrasing creates minor overlap risk with other data skills.	4 / 5
	Total	14 / 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/footprint/SKILL.md
Commit: f484c82

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