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

anthropic

Anthropic integration. Manage data, records, and automate workflows. Use when the user wants to interact with Anthropic 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/anthropic/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 a well-structured, actionable guide with executable commands and a solid connection-state feedback loop. Its main weaknesses are an unnecessary introductory explanation of Anthropic/Claude and no use of separate reference files for the API tables.

Suggestions

Remove or trim the opening paragraph explaining what Anthropic and Claude are; Claude already knows this and it consumes context tokens.

Fill in the empty Description cells in the Popular actions table so the entries are self-explanatory without running membrane action list.

Add a brief validation step after running actions (e.g. check the output field and HTTP status) to close the workflow feedback loop for the run/proxy sections.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Anthropic and Claude are ("AI safety and research company... competitor to OpenAI's GPT models") — concepts Claude already knows — which is more than minor padding, though the rest is a lean command reference.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands appear throughout (membrane connection ensure, action run, request proxy) with a full options table; minor gaps remain such as placeholder CONNECTION_ID values and empty description cells in the Popular actions table.	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence includes an explicit feedback loop for connection state (poll --wait, handle CLIENT_ACTION_REQUIRED, re-poll until READY), with only a minor validation gap after running actions.	4 / 5
Progressive Disclosure	Content is well organized into clear, navigable sections, but with no bundle files everything is inlined in one ~150-line file and no one-level-deep references are used to split out the action or proxy reference material.	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 covers both what and when with a clear vendor niche, but relies on generic action verbs and misses common natural terms like Claude. It is functional but lacks specificity and trigger breadth.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Send messages, list models, count tokens, and manage message batches via the Anthropic API."

Add natural trigger terms users actually say, such as "Claude", "Claude API", or "message batches", alongside "Anthropic data".

Tighten the "when" clause to concrete scenarios, e.g. "Use when the user wants to send Claude messages, list models, or batch API requests."

Dimension	Reasoning	Score
Specificity	It names the domain ("Anthropic integration") but the actions "Manage data, records, and automate workflows" are generic and abstract rather than concrete, matching the anchor for minimal/generic actions.	2 / 5
Completeness	Both a "what" (Anthropic integration that manages data/records/workflows) and an explicit "when" ("Use when the user wants to interact with Anthropic data") are present, though each is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	"Anthropic" is a natural keyword and "interact with Anthropic data" is a usable trigger, but common variations like Claude or Claude API are missing and "manage data, records" is jargon users would not naturally say.	3 / 5
Distinctiveness Conflict Risk	"Anthropic integration" is a clear vendor-specific niche with distinct triggers and minimal conflict risk, with only minor overlap from the generic "manage data" phrasing.	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/anthropic/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.