Name: basecone
Rating: 61.6 (1 reviews)
Author: membranedev

basecone

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

Quality

72%

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

Quality

Content

82%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 concrete CLI commands and a solid connect-and-poll workflow including error-state handling. Weaknesses are minor: a few padded phrases and an inconsistent step-numbering scheme that references an undefined 'Step 2'.

Suggestions

Fix the step numbering: define explicit 'Step 1'/'Step 2' labels (or drop them) so the 'skip to Step 2' and '1b' references resolve clearly.

Trim marketing-style filler ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') to tighten token efficiency.

Merge or clearly differentiate 'Searching for actions' and 'Popular actions', which currently repeat the same action-list discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste-ready bash commands throughout, containing only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing'—fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than a 5 because of a few padded marketing-style phrases.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request proxy) with a complete flag table for proxy requests, covering the common cases.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with a validation checkpoint (--wait polling) and a feedback loop for CLIENT_ACTION_REQUIRED, but the unexplained 'Step 2' and '1b' references are a minor sequencing gap.	4 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no bundle files to reference; structure is good with only minor organization gaps (the 'Popular actions' section partially overlaps with 'Searching for actions').	4 / 5
	Total	17 / 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 correctly uses third person and covers both what and when, anchored to a specific named app. Its main weakness is generic action verbs and thin trigger-term coverage, which cap it just above the midpoint.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Basecone-specific actions such as 'scan and extract invoice data, manage documents, and run approval workflows'.

Broaden the trigger clause with natural variations, e.g. 'Use when the user mentions Basecone, invoice processing, or document management in Basecone'.

Tighten the 'when' to name concrete scenarios (invoices, purchase/sales invoices, document types) rather than the generic 'interact with Basecone data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Basecone integration') and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like extracting or scanning—matching the anchor for domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	Both 'what' (Basecone integration, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with Basecone data') are present and explicit, though the 'when' could be more specific—matching the both-present-but-could-be-sharper anchor.	4 / 5
Trigger Term Quality	The only natural keyword is 'Basecone' / 'Basecone data'; it lacks synonyms or common variations users might say, fitting the anchor for some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	Basecone is a named niche application so conflict risk is low, but the trigger phrasing is minimal rather than a comprehensive set of distinct triggers, placing it mostly-distinct with minor overlap risk.	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/basecone/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.