Name: core-actionbook
Rating: 62.4 (1 reviews)
Author: actionbook

core-actionbook

Internal support skill for actionbook MCP selectors used by Rust documentation research workflows. Use only when another rust-skills workflow explicitly requests actionbook-backed selectors.

Quality

78%

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

Quality

Content

78%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 a concise, well-organized reference for two MCP tools with concrete parameters and an example payload, held back only by mild section duplication and the absence of a worked invocation example.

Suggestions

Merge the Workflow and MCP Tools bullets for search_actions/get_action_by_id to remove the duplicated descriptions.

Add a short worked example showing an actual search_actions call and how its returned ID feeds into get_action_by_id.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence, but the Workflow and MCP Tools sections repeat the same two tools with overlapping descriptions, a minor instance of content that could be trimmed.	4 / 5
Actionability	Parameters, types, defaults, required fields, and a concrete example response give actionable guidance, but there is no full example invocation of either MCP tool, leaving a minor gap.	4 / 5
Workflow Clarity	The three-step search -> get -> execute sequence is clear and unambiguous; no validation checkpoints are needed for read-only retrieval, but the lack of any error-handling guidance keeps it just below the top anchor.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files and no need for external references, the body is organized into clearly labeled sections (Workflow, MCP Tools, Parameters, Example Response), meeting the simple-skill exception for top marks.	5 / 5
	Total	17 / 20 Passed

Description

67%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 well-structured with clear what-and-when guidance and a tightly scoped, low-conflict niche, but its trigger terms lean on internal jargon rather than natural user phrasing and it names few concrete actions.

Suggestions

Add one or two concrete verbs (e.g., 'search and retrieve browser-automation selectors') so the capability reads as actions, not just a role.

Soften the trigger phrasing with at least one natural term (e.g., 'browser automation selectors' or 'Rust docs scraping') so it is less reliant on internal jargon.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ("actionbook MCP selectors used by Rust documentation research workflows") but describes a supporting role rather than listing multiple concrete actions, so it sits at the domain-named-with-limited-actions anchor rather than comprehensive.	3 / 5
Completeness	It states both what the skill is ("Internal support skill for actionbook MCP selectors") and an explicit, concrete when clause ("Use only when another rust-skills workflow explicitly requests actionbook-backed selectors"), matching the explicit what-and-when anchor.	5 / 5
Trigger Term Quality	Trigger language is heavily technical jargon ("actionbook MCP selectors", "rust-skills workflow") with only a couple of recognizable terms (Rust, documentation); it lacks the natural phrases a user would actually say, fitting the minimal-keywords anchor.	2 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped to actionbook selectors for Rust research and gated on an explicit request from another workflow, giving it distinct triggers with minimal overlap risk.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: actionbook/rust-skills
Path: skills/core-actionbook/SKILL.md
Commit: 5c40d3a

Reviewed: 7 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.