Name: werkbonapp
Rating: 60.8 (1 reviews)
Author: membranedev

werkbonapp

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

Quality

71%

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

Quality

Content

76%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 with concrete, copy-paste CLI guidance and good structural organization, but its workflows lack validation/verification checkpoints for destructive operations and carry minor verbosity and redundancy. Adding explicit verify steps and tightening the intro would raise the weaker dimensions.

Suggestions

Add an explicit validation/verification checkpoint before and after destructive operations — e.g. before running a mutating action or proxy POST/PUT/DELETE, confirm the target id, and after, re-fetch the resource to verify the change took effect.

Trim the introductory paragraph explaining what WerkbonApp / field service management is, since Claude can infer the domain from the named integration; keep only what is needed to orient the workflow.

Merge the redundant 'Popular actions' section into 'Searching for actions' to remove the duplicated `action list` discovery command.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable CLI commands and a flags table, with only minor over-explanation such as the introductory paragraph on what WerkbonApp is and phrases like 'This is the fastest way to get a connection' that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests plus a complete flags table, covering the common integration cases with real executable invocations.	5 / 5
Workflow Clarity	There is a clear sequence with polling and state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the skill drives destructive operations (action run, proxy POST/PUT/PATCH/DELETE) with no validation or verify-checkpoint before/after them, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The skill is self-contained with well-organized section headers and no nested references, but it exceeds 50 lines and has a minor redundancy ('Popular actions' repeats the discovery command from 'Searching for actions'), placing it just below the level-5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

66%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 cleanly answers both what and when and is highly distinct thanks to the named-app niche, but its capability verbs and trigger-term coverage are generic and could be more concrete and varied. Strengthening the action list and adding natural synonyms would lift the weaker dimensions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete WerkbonApp actions such as 'create and update work orders, fill checklists, attach materials and photos, and capture signatures'.

Expand the 'Use when...' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to manage WerkbonApp work orders, checklists, materials, or field-service reporting'.

Add common synonyms/variants of the trigger (e.g. 'work orders', 'field service tickets', 'werkbonnen') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('WerkbonApp integration') plus two actions ('Manage data, records' and 'automate workflows'), but the actions are generic rather than concrete — closer to 'Processes PDF files and extracts content' than to a comprehensive multi-action list.	3 / 5
Completeness	It states what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with WerkbonApp data'), but the when is a single generic trigger rather than concrete trigger phrases, so it sits below the level-5 anchor.	4 / 5
Trigger Term Quality	The phrase 'interact with WerkbonApp data' surfaces the app name as a keyword, but coverage is thin with no synonyms or natural variations a user might say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to a named application ('WerkbonApp') creates a clear niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/werkbonapp/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.