Name: snipe-it
Rating: 62.4 (1 reviews)
Author: membranedev

snipe-it

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

Quality

74%

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/snipe-it/SKILL.md

Quality

Content

86%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 content is highly actionable with executable commands and a well-checkpointed connection workflow, organized cleanly in a single file. The main improvements are minor conciseness trims and fixing the inconsistent step numbering in the connection section.

Suggestions

Consolidate the duplicate 'membrane action list --intent=QUERY' examples in 'Searching for actions' and 'Popular actions' to remove redundancy.

Fix the connection-section numbering: label the action-running section as 'Step 2' and renumber '1b' to follow an explicit '1a' so cross-references resolve.

Tighten the 'Agent Types' line into a concise inline list rather than a trailing explanatory sentence.

Dimension	Reasoning	Score
Conciseness	The body is efficient and mostly assumes Claude's competence, with only minor redundancy (the action-list command appears twice with slight variation) and a loose 'Agent Types' line that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready executable commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a flags table, with clearly parameterized placeholders.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checkpoints and a poll-act-repoll feedback loop, but step labeling is inconsistent ('Step 2' is referenced but unlabeled, and '1b' appears without a '1a').	4 / 5
Progressive Disclosure	No bundle files are needed; the single-file body is well-organized with clear section headers and all content appropriately inline, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 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 correctly pairs a 'what' and a 'when' and anchors on a distinct named product, but the action language is generic rather than Snipe-IT-specific and trigger-term coverage is thin. Tightening the actions to concrete asset/license tasks and adding natural trigger synonyms would raise it.

Suggestions

Replace generic verbs with Snipe-IT-specific actions, e.g. 'Track hardware assets, manage software licenses, and audit accessories.'

Expand the 'Use when' clause with concrete user phrases, e.g. 'Use when the user wants to track assets, manage licenses, or query Snipe IT records.'

Add a natural synonym such as 'IT asset management (Snipe-IT)' so the skill triggers on broader phrasings.

Dimension	Reasoning	Score
Specificity	Names the Snipe IT domain with a few actions ('Manage data, records, and automate workflows') but they are generic rather than concrete Snipe-IT-specific operations like tracking assets or managing licenses.	3 / 5
Completeness	States both a clear 'what' ('Snipe IT integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Snipe IT data'), though the trigger phrasing is somewhat generic.	4 / 5
Trigger Term Quality	The keyword 'Snipe IT' is exactly what a user would say, but coverage lacks natural synonyms or variants such as 'asset management', 'hardware tracking', or file extensions.	3 / 5
Distinctiveness Conflict Risk	The named product 'Snipe IT' gives a clear niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' overlay leaves minor overlap with related integration 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/snipe-it/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.