Name: handwrytten
Rating: 66.4 (1 reviews)
Author: membranedev

handwrytten

Handwrytten integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Handwrytten data.

Quality

80%

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

Quality

Content

82%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.

A well-structured, highly actionable integration guide built around concrete Membrane CLI commands and a clear connection workflow with state-based checkpoints. Its chief weakness is modest verbosity and the absence of result-verification steps when running actions or proxying requests.

Suggestions

Trim mild filler phrases (e.g., 'so you can focus on the integration logic rather than auth plumbing') to improve token efficiency.

Add a verification step after running actions or proxy requests (e.g., inspect the `output` field or check for an error/status before declaring success) to strengthen the workflow's feedback loop.

Move the proxy flag reference table into a dedicated reference file or collapse it to the most common flags to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal concept over-explanation, but contains a few trimmable phrases ("so you can focus on the integration logic rather than auth plumbing", "Those will be used to adjust tooling to be used best with your harness"), fitting the efficient-with-minor-over-explanation anchor rather than the fully lean 5.	4 / 5
Actionability	Provides copy-paste-ready executable bash commands for every phase (login, connection ensure, action list/run, request proxy) with concrete flags and JSON examples covering common cases, matching the fully-executable top anchor.	5 / 5
Workflow Clarity	The connection setup sequence is clearly ordered with explicit state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-until-ready feedback loop, but running/proxy actions lack result verification checkpoints, so it sits just below the full-validation 5.	4 / 5
Progressive Disclosure	The single-file skill is well organized with clear section headers and no nested references, and no content clearly demands a separate file, but at ~150 lines it is longer than the under-50-line simple-skill case that scores 5 on structure alone, placing it at good-structure-with-minor-gaps.	4 / 5
	Total	17 / 20 Passed

Description

78%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.

A concise third-person description that clearly states both capability and trigger, with a distinct branded niche. Its main limitation is that the trigger phrasing is fairly generic and lacks the richer natural-term variations that would push it to the top anchor.

Suggestions

Expand the 'Use when' clause with more concrete natural triggers a user would actually say (e.g., 'send handwritten letters', 'manage Handwrytten contacts and campaigns', 'check order status').

Replace 'and more' with the next-most-important capability or drop it so coverage reads as comprehensive rather than open-ended.

Consider adding the most common file-format or action keywords (e.g., 'letters', 'stationery', 'handwritings') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete managed entity types ("Persons, Organizations, Deals, Leads, Activities, Notes"), but the trailing "and more" leaves minor coverage gaps, fitting the several-specific-actions-with-minor-gaps anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers both what ("Manage Persons, Organizations, Deals, Leads, Activities, Notes and more") and when ("Use when the user wants to interact with Handwrytten data"), but the when clause is somewhat generic and could be more specific, matching the both-present-but-when-could-be-more-explicit anchor rather than a clean 5.	4 / 5
Trigger Term Quality	Includes a natural "Use when the user wants to interact with Handwrytten data" phrase with the brand keyword, giving good coverage, but it lacks synonyms or variations a user might naturally say, so it stops short of the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The branded "Handwrytten integration" niche with its named entity set has distinct triggers and minimal overlap risk with other skills, matching the clear-niche-minimal-conflict anchor.	5 / 5
	Total	17 / 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/handwrytten/SKILL.md
Commit: f484c82

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