Name: woodpeckerco
Rating: 62.4 (1 reviews)
Author: membranedev

woodpeckerco

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

Quality

73%

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

Quality

Content

87%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 body is highly actionable with executable membrane commands and a well-sequenced, validated connection workflow, kept lean with minor trimmable commentary.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands and minimal concept padding, though phrases like 'This is the fastest way to get a connection' and 'This will burn less tokens' could be trimmed.	4 / 5
Actionability	Fully executable copy-paste-ready membrane commands with flags and JSON examples cover the common cases of auth, connection, action search/run, and proxying.	5 / 5
Workflow Clarity	Clear connection sequence (ensure -> poll/wait -> branch on state) with validation checkpoints and polling feedback for error recovery, just short of a full validate->fix->retry checklist.	4.5 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear section headers and no nested references; no bundle files exist, which is appropriate for this scope.	4.5 / 5
	Total	18 / 20 Passed

Description

60%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 covers both what and when with a clear Woodpecker.co niche, but its action list is generic and the trigger phrasing lacks synonyms or concrete variations.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Woodpecker.co actions like 'manage prospects, campaigns, and team members'.

Expand the trigger clause with natural variations: 'Use when the user wants to manage Woodpecker.co prospects, campaigns, or follow-ups.'

Dimension	Reasoning	Score
Specificity	Names the Woodpecker.co domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not concrete Woodpecker.co operations, landing between anchors 2 and 3.	2.5 / 5
Completeness	Explicitly answers both what ('Woodpecker.co integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Woodpecker.co data.'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the natural phrase 'interact with Woodpecker.co data' but lacks synonyms, common variations, or file extensions that anchor 4 would require.	3 / 5
Distinctiveness Conflict Risk	Clearly niched to Woodpecker.co with a distinct trigger, giving minimal conflict risk with other skills.	4 / 5
	Total	13.5 / 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/woodpeckerco/SKILL.md
Commit: f484c82

Reviewed: ~21 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.