Name: argyle
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

argyle

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

Quality

62%

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

Quality

Content

67%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 concrete and executable, with a connection workflow that includes real validation via state polling and error branching. Main gaps are mild background padding, a slightly loose step numbering, and an all-inline structure that a 140-line skill could partially offload to reference files.

Suggestions

Trim the opening background paragraph and the "auth plumbing" aside; assume Claude knows generic integration concepts.

Fix the step numbering (define explicit Step 1/Step 2 headings) so the dangling "Step 2" and lone "1b" references resolve.

Consider moving the clientAction field schema and the proxy flag table into a references/ file, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and flags, but the opening paragraph ("Argyle is a platform... used by lenders, landlords...") and phrases like "so you can focus on the integration logic rather than auth plumbing" add explanation Claude does not strictly need, matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It supplies copy-paste-ready commands for install, login, connection, polling, action list/run, and proxying plus a flag table, but examples rely on placeholders (CONNECTION_ID, <actionId>, /path/to/endpoint) without a concrete end-to-end run, fitting the mostly-executable-with-minor-gaps anchor.	4 / 5
Workflow Clarity	The connect-and-poll flow has explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) with a feedback loop (poll again after user action), but the step structure is loose — a dangling "Step 2" reference and a lone "1b" heading — keeping it below the crisp-checklist anchor.	4 / 5
Progressive Disclosure	Content is well organized with clear section headers and no nested references, but at ~140 lines with no bundle files everything is inline (e.g., the clientAction field breakdown and proxy flag table) rather than split into reference files, matching the good-structure-with-minor-organization-gaps anchor.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly uses third-person voice and includes an explicit "Use when" trigger, satisfying the completeness floor. Its weakness is generic action language ("manage data, records, automate workflows") that underspecifies what the skill concretely does with Argyle.

Suggestions

Replace generic verbs with concrete Argyle operations (e.g., "Fetch payroll and employment records, verify income, trigger payouts") to lift specificity.

Add natural trigger variations users might say (e.g., "payroll data", "employment verification", "income verification") beyond just "Argyle".

Tighten the "when" clause with concrete trigger phrases (e.g., "Use when the user asks to pull payroll data or verify employment through Argyle").

Dimension	Reasoning	Score
Specificity	It names the domain ("Argyle integration") but the actions — "Manage data, records, and automate workflows" — are generic categories rather than concrete operations, matching the anchor whose actions are minimal or generic.	2 / 5
Completeness	It provides both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Argyle data"), but the trigger phrasing is generic rather than concrete, so it sits below the explicit-concrete-triggers anchor.	4 / 5
Trigger Term Quality	The natural keyword "Argyle" appears ("Argyle integration", "interact with Argyle data") but coverage lacks synonyms or variations beyond repeating the product name, fitting the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named platform "Argyle" gives it a clear niche with minimal conflict risk, though the broad action verbs ("manage data", "automate workflows") create minor overlap with general integration skills.	4 / 5
	Total	13 / 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/argyle/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.