Name: niftykit
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

niftykit

NiftyKit integration. Manage Organizations, Users. Use when the user wants to interact with NiftyKit data.

Quality

61%

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

Quality

Content

61%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 solid, command-driven integration guide with good actionability and clear sectioning. Its main gaps are the absence of validation/verification steps around destructive proxy operations and some light introductory padding.

Suggestions

Add an explicit validation checkpoint after connecting and before destructive proxy calls, e.g. verify the connection with a read-only `membrane action list` or a GET request before issuing POST/PUT/DELETE.

Trim the introductory NiftyKit/Membrane background to one line each, since Claude can infer the platform context once the commands are present.

Show one complete worked example (search → connect → list actions → run with JSON input) so the end-to-end flow is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but the intro ("NiftyKit is a platform that helps creators launch and manage NFT collections...") and the auth aside ("so you can focus on the integration logic rather than auth plumbing") add explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands (install, login, search, connect, action list/run) plus a full proxy flag table and a JSON input example; placeholder IDs like CONNECTION_ID are expected and the only minor gap is no worked end-to-end example.	4 / 5
Workflow Clarity	The install→login→connect→discover→run sequence is clear, but there are no validation checkpoints, and the proxy enables destructive methods (POST/PUT/PATCH/DELETE) with no verify step, triggering the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	Content is organized into well-labeled sections with no nested or buried references, and a single file is appropriate here given no bundle files exist; it falls short of 5 only because there is no progressive disclosure mechanism to split the longer proxy/action reference material.	4 / 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 is adequately functional: it names the platform, lists two managed entities, and includes an explicit 'Use when' trigger covering both what and when. Its weakness is generic action verbs and a thin trigger phrase that misses the natural NFT-specific vocabulary users would actually say.

Suggestions

Replace the generic verb "Manage" with concrete actions the skill actually supports, e.g. "Create and manage Collections, Contracts, Drops, Claims, and Wallets" to align with the documented hierarchy.

Expand the trigger clause to include natural user phrases, e.g. "Use when the user wants to mint or distribute NFTs, manage NiftyKit collections, drops, or wallets, or interact with NiftyKit data."

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete entities ("Manage Organizations, Users") but the verb "Manage" is generic and the named entities don't match the skill's actual Collection/Contract/Drop capabilities, so it lands at the 1-2-concrete-actions anchor rather than comprehensive.	3 / 5
Completeness	It states both what ("Manage Organizations, Users") and when ("Use when the user wants to interact with NiftyKit data"), matching the has-both-but-when-could-be-more-explicit anchor; the trigger is generic enough to stop short of a 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with NiftyKit data" provides a relevant trigger keyed on the platform name, but it lacks the natural synonyms and variations (minting, collections, NFTs, drops) a user would actually say.	3 / 5
Distinctiveness Conflict Risk	Being tied to a named platform ("NiftyKit") makes it mostly distinct with minimal overlap risk, but the thin description lacks the rich distinct triggers of the 5-anchor example.	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/niftykit/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.