Name: docraptor
Rating: 48 (1 reviews)
Author: membranedev

docraptor

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

Quality

51%

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/docraptor/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 content is a well-structured, actionable guide to driving DocRaptor via the Membrane CLI, with strong command coverage and a clear connection state machine. Its main weaknesses are mild over-explanation, a broken 'Step 2' reference in the workflow, and the absence of validation/verification for action execution.

Suggestions

Fix the workflow numbering: label 'Searching for actions' as 'Step 2' (or renumber 1b) so the 'skip to Step 2' reference resolves, and add an explicit 'Verify the output' checkpoint after running an action.

Trim the opening conceptual paragraph and rhetorical padding ('so you can focus on the integration logic...') since Claude already understands auth and CLI fundamentals.

Add one end-to-end worked example (e.g. create-document with a concrete HTML payload) and resolve the <agentType> placeholder with the actual accepted values.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command blocks and tables, but includes unnecessary explanatory prose such as the opening 'DocRaptor is a service that converts...' paragraph and 'so you can focus on the integration logic rather than auth plumbing' padding that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxying, plus a JSON input example and an action table; minor gaps remain (e.g. unresolved <agentType> placeholder and no end-to-end create-document example with a real payload).	4 / 5
Workflow Clarity	The connection workflow has useful state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) with a re-poll feedback loop, but it references a 'Step 2' that is never labeled, uses an unexplained '1b' numbering, and provides no validation/verification for the action-run step.	3 / 5
Progressive Disclosure	No bundle files are present, and the single SKILL.md is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) and no nested references; minor gaps only, as some inline reference tables could live in separate files.	4 / 5
	Total	14 / 20 Passed

Description

41%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 includes a 'Use when...' trigger and ties the skill to a distinct named service, but its capability statement is vague and omits DocRaptor's core PDF/document-generation purpose and natural user keywords. Tightening the 'what' with concrete actions and common trigger phrases would substantially improve it.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete DocRaptor actions such as 'Generate PDFs, XLS, and XLSX documents from HTML or URLs, create hosted documents, and check document status.'

Expand the trigger clause to include natural user phrases, e.g. 'Use when the user wants to generate a PDF from HTML, create invoices or reports, or convert web content to a downloadable document.'

Mention the supported formats (PDF, XLS, XLSX) and hosted/async options so the description reflects the skill's real coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('DocRaptor integration') but its actions are generic ('Manage data, records, and automate workflows') rather than concrete DocRaptor capabilities like PDF generation or HTML conversion, matching the anchor for minimal/generic actions.	2 / 5
Completeness	It has both a 'what' and a 'Use when...' clause, but the 'what' is vague and never states DocRaptor's actual purpose (PDF/document generation), so it falls below the 'clear what' bar despite the trigger being present.	3 / 5
Trigger Term Quality	Beyond the brand name 'DocRaptor', the only keywords are generic ('data', 'records', 'workflows'); the natural phrases users would actually say ('generate a PDF', 'convert HTML to PDF', 'create a document') are absent.	2 / 5
Distinctiveness Conflict Risk	The 'DocRaptor' brand name gives it a clear, distinct niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing introduces minor overlap with broad data skills.	4 / 5
	Total	11 / 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/docraptor/SKILL.md
Commit: f484c82

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