Name: techwolf
Rating: 59.2 (1 reviews)
Author: membranedev

techwolf

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

Quality

68%

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

Quality

Content

75%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 Membrane CLI commands and a clear connection state-machine, supported by decent sectioning and progressive structure. Its main weakness is conciseness — a marketing-style intro and some padded phrasing — plus a couple of unclear cross-references ('Step 2').

Suggestions

Trim the opening paragraph to one factual sentence about TechWolf and remove marketing phrasing like 'strategic workforce planning' and 'focus on the integration logic rather than auth plumbing'.

Define or relabel the 'Step 2' reference (e.g. rename to 'Searching for actions') so the 'skip to Step 2' cross-references resolve.

Add an explicit validation checkpoint after running an action (e.g. 'Check the output field; if empty or error, re-run action list to confirm parameters') to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening marketing paragraph ('helps companies understand and leverage the skills...', 'strategic workforce planning') and phrases like 'so you can focus on the integration logic rather than auth plumbing' add explanation that could be trimmed, matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases — install, login, connection ensure, polling, action list/run, and proxy requests with concrete flags — matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with an explicit state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-polling, but 'skip to Step 2' references an undefined Step 2 and action-run results are not explicitly validated, so it sits just below the explicit-checklist 5 anchor.	4 / 5
Progressive Disclosure	The single file is well organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no nested references, but at ~158 lines the inlined clientAction spec and proxy-flag table could live in a reference file, fitting the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	16 / 20 Passed

Description

62%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 is third-person, concise, and answers both what and when with an explicit 'Use when' clause, but its action vocabulary is generic and its trigger terms are narrow for a niche platform. Tightening the actions and broadening trigger phrasing would raise specificity and trigger_term_quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete TechWolf operations such as 'search and extract skills, browse the skill taxonomy, and run skill-extraction jobs'.

Expand the trigger clause with natural phrasings users would say, e.g. 'Use when the user wants to query TechWolf skills, map employee skills, or extract skills from job postings'.

Add a file/record cue (e.g. 'TechWolf records, skill extractions, or taxonomy lookups') to improve distinctiveness from generic data skills.

Dimension	Reasoning	Score
Specificity	Names the TechWolf domain plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete API-level operations, fitting the anchor for domain + 1-2 actions that are not comprehensive.	3 / 5
Completeness	Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with TechWolf data'), landing at the anchor where both are present but the trigger could be more specific; not a 5 because the trigger phrases are narrow.	4 / 5
Trigger Term Quality	Contains the natural platform phrase 'interact with TechWolf data' but offers few synonyms or variations a user might say, matching the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	The named platform 'TechWolf' gives it a clear niche with minimal conflict risk, but the generic verbs 'data, records, workflows' leave minor overlap with other data-management skills, so it sits just below the minimal-conflict 5 anchor.	4 / 5
	Total	14 / 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/techwolf/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.