Name: archbee
Rating: 60.8 (1 reviews)
Author: membranedev

archbee

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

Quality

71%

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/archbee/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 content is highly actionable with concrete commands and good validation feedback in the connection workflow, held back only by minor verbosity, inconsistent step numbering, and inline reference material that could be split out.

Suggestions

Fix the step numbering (add a labeled '1a'/'Step 2') so the 'skip to Step 2' references resolve, or renumber as a single flat sequence.

Trim the marketing-style intro paragraph ('built for software teams... used by developers, product managers, and technical writers') and the redundant 'Popular actions' section that restates the earlier discovery command.

Dimension	Reasoning	Score
Conciseness	The body is largely lean command-driven content with a flags table and code blocks, with only minor over-explanation (e.g., the marketing-style intro paragraph and the redundant 'Popular actions' section restating discovery), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a flags table and JSON examples, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with validation checkpoints (poll until READY, CLIENT_ACTION_REQUIRED handling, CONFIGURATION_ERROR checks), but step labels are inconsistent ('1b' with no '1a', 'Skip to Step 2' with no labeled Step 2), so it falls just short of the explicit-feedback-loop polish of a 5.	4 / 5
Progressive Disclosure	No bundle files exist, so all content lives in this one well-sectioned SKILL.md; it is well-organized but the inlined flags table and full clientAction schema details are content that could plausibly live in a separate reference, matching 'good structure; most content appropriately placed; minor organization gaps' rather than a clean one-level-deep split of a 5.	4 / 5
	Total	17 / 20 Passed

Description

61%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 is and when to use it, and its product-specificity makes conflict risk low, but the capability list is generic and trigger coverage is thin.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Archbee capabilities (e.g., search documents, create/update blocks, manage spaces and collections).

Broaden the trigger clause with natural phrasing users would actually say, e.g. 'Use when the user wants to search, read, or update Archbee docs, spaces, or API documentation.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Archbee integration') but the actions ('Manage data, records, and automate workflows') are generic abstractions rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It states both what ('Archbee integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Archbee data.'), but the 'when' is generic and could be more explicit/specific, matching the 4 anchor rather than the concrete-trigger-phrases of a 5.	4 / 5
Trigger Term Quality	The product name 'Archbee' is a relevant keyword carried in a Use-when clause, but no synonyms, natural phrase variations, or file extensions appear, fitting 'some relevant keywords but missing common variations or synonyms' rather than the fuller coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	The product-specific 'Archbee' anchor gives it a clear niche with a distinct trigger unlikely to fire for unrelated skills, matching 'clear niche with distinct triggers; minimal conflict risk'.	5 / 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/archbee/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.