Name: wrk
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

wrk

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

Quality

67%

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/wrk/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 highly actionable with concrete CLI commands and a useful connection-state workflow, but it is held back by some conceptual padding, a redundant Popular actions section, a dangling "Step 2" reference, and missing verification steps for destructive proxy/action operations.

Suggestions

Add a verification checkpoint after action runs and proxy requests (e.g., re-fetch or inspect the returned output) since these support destructive HTTP methods.

Fix the broken "Step 2" reference by numbering the post-connection steps (search actions, run actions) or removing the dangling reference.

Remove the conceptual Wrk intro paragraph and merge the redundant "Popular actions" section into "Searching for actions" to tighten token usage.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but it opens with a conceptual paragraph explaining what Wrk is, includes commentary like "so you can focus on the integration logic rather than auth plumbing", and repeats the action-discovery command across "Searching for actions" and a thin "Popular actions" section — unnecessary explanation that could be tightened.	3 / 5
Actionability	It provides many concrete, executable commands with real flags (install, login, connection ensure/get --wait, action list/run, request) plus a proxy flags table; minor gaps remain in the generic '{"key": "value"}' input placeholder, the absence of a worked end-to-end example with a real action name, and the redundant "Popular actions" section.	4 / 5
Workflow Clarity	A clear sequence exists for connection setup with a polling/state feedback loop, but the body references "Step 2" which is never labeled, and the action-run and proxy workflows (which support destructive POST/PUT/DELETE) have no verification checkpoints — the destructive-operation cap holds this at 3.	3 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references; because no bundle files exist and the skill exceeds the ~50-line simple-skill threshold, it stops short of 5, but the structure and navigation are solid with only minor gaps such as the redundant "Popular actions" section.	4 / 5
	Total	14 / 20 Passed

Description

73%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 states what the skill does and when to use it, and the named "Wrk" platform keeps conflict risk low. Its main weakness is generic action verbs and a narrow trigger clause that could name the concrete record types the body later enumerates.

Suggestions

Replace generic verbs with concrete actions, e.g. "Manage tasks, comments, time entries, clients, and invoices; automate workflows."

Expand the "Use when..." clause to list concrete triggers such as "when the user wants to manage Wrk tasks, projects, time entries, clients, or invoices".

Drop filler phrasing like "Wrk integration." to tighten the opening.

Dimension	Reasoning	Score
Specificity	It names the Wrk domain and a few actions ("Manage data, records, and automate workflows"), but the verbs are generic ("manage", "automate") rather than concrete like extract/fill/merge, so it stops at naming domain plus a couple of actions without being comprehensive.	3 / 5
Completeness	Both "what" (Wrk integration; manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Wrk data") are explicitly present, but the "when" clause is narrow and could enumerate concrete triggers, matching the anchor where both exist yet "when" could be more specific.	4 / 5
Trigger Term Quality	Natural terms a user would say are present ("Wrk", "data", "records", "workflows", "interact with Wrk data"), giving good keyword coverage; a few synonyms or task-specific terms (e.g., invoices, time entries) are missing, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	"Wrk" is a named platform with a distinct trigger ("interact with Wrk data"), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/wrk/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.