Name: traceable
Rating: 58.4 (1 reviews)
Author: membranedev

traceable

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

Quality

67%

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

Quality

Content

72%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 concrete and actionable with executable commands and a clear connection state machine, but its workflow sequencing is undermined by broken step numbering (a referenced but unlabeled Step 2) and missing validation checkpoints after action execution. Progressive disclosure is clean given the single-file, well-sectioned structure.

Suggestions

Fix the step numbering: either label an explicit "Step 2" section that the "skip to Step 2" references point to, or relabel the phases as a coherent numbered sequence.

Add validation checkpoints after running actions and proxy requests (e.g. check the `output`/response status, handle error fields) so the workflow has explicit feedback loops.

Trim minor motivational prose such as "so you can focus on the integration logic rather than auth plumbing" to keep the body lean.

Dimension	Reasoning	Score
Conciseness	The body is command-and-example driven and largely efficient, with only minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection", fitting the efficient-minor-trimmable anchor rather than the noticeably-verbose 2 or the fully-lean 5.	4 / 5
Actionability	It provides concrete executable commands throughout (install, login, connection ensure, action run, request) with flags, JSON examples, and a flags table, with only minor gaps from placeholders like CONNECTION_ID and QUERY, matching the mostly-executable-minor-gaps anchor.	4 / 5
Workflow Clarity	The install-auth-connect-poll-search-run sequence and the connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) provide a clear sequence, but step numbering is broken ("skip to Step 2" with no labeled Step 2, a lone "1b") and there are no validation checkpoints after running actions or proxy requests, matching the steps-present-but-checkpoints-missing anchor.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained SKILL.md with clear, well-organized section headers (Overview, Working with Traceable, Install, Authentication, Connecting, Searching, Popular actions, Best practices) and one level of structure, which the simple-skill note allows to score 5.	5 / 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 covers both what and when with an explicit trigger clause, but its action verbs are generic and it lacks concrete Traceable-specific task terms. It is mostly distinct from other skills thanks to the Traceable naming.

Suggestions

Replace generic verbs like "Manage data, records" with concrete Traceable actions such as "query traces and events, review API security findings, automate workflows".

Add natural trigger terms users would say, e.g. "Use when the user wants to inspect Traceable traces, events, or API security alerts."

Tighten the "when" clause to reference specific Traceable objects (traces, events) so it does not read as a generic data-management skill.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Traceable domain plus a couple of actions, but "Manage data" and "Manage records" are generic, so coverage is not comprehensive — fitting the 1-2 concrete actions anchor rather than 4's several specific actions.	3 / 5
Completeness	It answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Traceable data"); the trigger clause is explicit but could be more specific about concrete Traceable tasks, matching the both-present-could-be-more-explicit anchor.	4 / 5
Trigger Term Quality	"Traceable", "data", "records", and "interact with Traceable data" give some relevant keywords, but common variations, synonyms, and concrete task terms (traces, events, API security) are missing, matching the some-relevant-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	"Traceable integration" and "interact with Traceable data" carve a clear niche, though the generic "Manage data, records" phrasing leaves minor overlap risk with other data-management skills, matching the mostly-distinct-minor-overlap 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/traceable/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.