Name: api-ninjas
Rating: 55.2 (1 reviews)
Author: membranedev

api-ninjas

API Ninjas integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with API Ninjas 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/api-ninjas/SKILL.md

Quality

Content

66%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, actionable single-file skill with executable CLI commands, a well-sequenced connection workflow, and clear section organization. It loses points mainly on conciseness due to some padded prose and could tighten validation checkpoints for batch/run operations.

Suggestions

Trim the introductory 'API Ninjas Overview' and redundant best-practice prose to reduce tokens while preserving the executable commands.

Add an explicit validation/check step after running actions (e.g. inspect the `output` field and handle errors) to strengthen the run-workflow feedback loop.

Consider moving the full Popular actions table to a reference file and keeping only a few key examples inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes some unnecessary explanatory prose (e.g. the API Ninjas overview section and reworded best-practice paragraphs) that could be tightened, matching the anchor for mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for install, login, connecting, searching, running, and proxying with a useful actions table, with only minor gaps such as placeholder CONNECTION_ID not fully bridged, fitting the anchor for mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The connect-and-poll workflow is clearly sequenced with state handling (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, though the destructive/batch guidance relies on best-practice bullets rather than explicit validation checkpoints, matching clear sequence with most checkpoints present.	4 / 5
Progressive Disclosure	Content is well organized into clear sections (Overview, Working, Popular actions, Best practices) with the bulk action catalog inlined appropriately for a single-file skill and no nested references; minor organization gaps keep it just below a 5, matching good structure with most content appropriately placed.	4 / 5
	Total	15 / 20 Passed

Description

60%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 a distinct niche and includes both 'what' and 'when' guidance, but the capabilities are described too generically ('Manage') and the trigger terms lack natural synonym coverage. Tightening the action verbs and adding common user phrasings would raise specificity and trigger quality.

Suggestions

Replace the generic verb 'Manage' with concrete actions users perform (e.g. 'look up IP addresses, validate emails, analyze sentiment, fetch weather').

Expand trigger terms with natural phrasings users actually say, such as 'weather data', 'email validation', 'WHOIS lookup', or 'sentiment analysis'.

Reframe the 'when' clause to list specific scenarios (e.g. 'Use when the user needs IP geolocation, text similarity, email validation, or weather data') for sharper triggering.

Dimension	Reasoning	Score
Specificity	Names the domain (API Ninjas) and lists entity types ('Organizations, Users, Goals, Filters') but the actions are minimal and generic ('Manage') without concrete operations, matching the anchor for naming a domain with minimal actions.	2 / 5
Completeness	It has a clear 'what' ('Manage Organizations, Users, Goals, Filters') and an explicit 'when' ('Use when the user wants to interact with API Ninjas data'), though the 'when' could be more specific about which triggers, matching the anchor for both present but 'when' could be more explicit.	4 / 5
Trigger Term Quality	It includes some relevant keywords ('API Ninjas', 'interact with API Ninjas data') but misses common natural variations and synonyms users would say, fitting the anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The description is tied to a clear niche (API Ninjas integration) with distinct triggers and minimal conflict risk with other skills, matching the anchor for a clear niche with distinct triggers.	5 / 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/api-ninjas/SKILL.md
Commit: f484c82

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