Name: apitemplateio
Rating: 59.2 (1 reviews)
Author: membranedev

apitemplateio

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

Quality

69%

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

Quality

Content

81%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 and the connection workflow is exemplary in its state-based checkpoints and feedback loops. The main gaps are minor conciseness trims in the intro/overview and a lack of concrete per-action input/output examples and proxy path examples.

Suggestions

Trim the intro paragraph and the empty Overview list to essentials; Claude already understands what a PDF/image generation SaaS is.

Add at least one concrete proxy example (e.g. 'membrane request CONNECTION_ID /v1/create-pdf -d {...}') instead of the placeholder '/path/to/endpoint'.

Include a short worked example for one popular action (e.g. create-image) showing realistic --input JSON and the expected output field.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands, tables, and state-handling bullets, but the intro paragraph ('APITemplate.io is a SaaS platform that automates image and PDF generation using APIs. It's used by marketers, developers, and businesses...') and the near-empty Overview list are minor over-explanation that could be trimmed.	4 / 5
Actionability	Executable membrane commands and a popular-actions table with keys provide copy-paste-ready guidance for the common workflow, but the proxy section uses a placeholder path ('/path/to/endpoint') and there are no per-action input/output examples, leaving minor gaps below a clear 5.	4 / 5
Workflow Clarity	The connection workflow is explicitly sequenced with validation checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and feedback loops ('After the user completes the action... poll again'), matching the anchor for clear sequence with explicit validation and error recovery.	5 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but it is well-organized into clear sections (Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices); the inlined popular-actions and proxy-flag tables are reasonably placed, leaving only minor organization gaps versus a clean 5.	4 / 5
	Total	17 / 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 is grammatically sound and includes both a capability statement and an explicit trigger clause, but its action vocabulary is generic rather than APITemplate-specific. Tightening it with concrete operations (PDF/image generation, templates) and richer trigger phrases would lift specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete APITemplate actions, e.g. 'Create PDFs and images from templates, merge PDFs, manage generated objects.'

Expand the trigger clause to surface natural user phrases: 'Use when the user wants to create PDFs or images, generate documents from HTML/URL, or merge PDFs via APITemplate.io.'

Mention template/JSON data inputs in the description so the trigger matches real user requests more precisely.

Dimension	Reasoning	Score
Specificity	The description names the domain ("APITemplate.io integration") but its actions are minimal and generic ("Manage data, records, and automate workflows") rather than concrete APITemplate operations like creating PDFs or generating images, so it sits below the midpoint between anchors 2 and 3.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with APITemplate.io data") are present, but the 'when' could be more specific since it omits PDFs, images, and templates, fitting the anchor just below 5.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ("APITemplate.io", "data", "records", "workflows") but misses the natural phrases users would actually say ("create PDF", "generate image", "from template/HTML/URL"), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The trigger is anchored to the distinct APITemplate.io niche, giving minimal conflict risk, though the generic action verbs leave minor overlap with other data-integration skills, so it is not a clear 5.	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/apitemplateio/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.