Name: encore
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

encore

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

Quality

68%

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

Quality

Content

75%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 — concrete, executable Membrane commands with a clear connection-state feedback loop — and well structured. Its main weaknesses are a confusing, unrelated overview block and a wrong official-docs URL, plus inconsistent step numbering that slightly muddies the workflow.

Suggestions

Remove or replace the bogus 'Encore Overview' section (Project/Track/Clip/Member/User) and the Spotify Web API docs URL — both appear copy-pasted from an unrelated skill and mislead the model.

Fix the inconsistent step numbering: the body references 'Step 2' but labels the wait step '1b' with no Step 1; renumber the connecting flow coherently.

Tighten prose in Authentication and Best practices (e.g., drop 'so you can focus on the integration logic' and correct 'burn less tokens' to 'burn fewer tokens') to reclaim tokens.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient command reference, but it includes unnecessary prose ('so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens...') and an unrelated, confusing 'Encore Overview' block (Project/Track/Clip/Member/User) that pads the context, matching 'mostly efficient but includes some unnecessary explanation that could be tightened'.	3 / 5
Actionability	The body is dominated by concrete, copy-paste-ready commands with exact flags and a flag reference table — 'membrane connection ensure "https://encore.dev/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --json' — fully covering the common cases, matching the level-5 anchor.	5 / 5
Workflow Clarity	The connection flow has an explicit, sequenced state-checking feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED with re-polling), giving clear checkpoints; it stops at 4 rather than 5 because step numbering is inconsistent ('#### 1b', a referenced 'Step 2' with no matching Step 1) and pre-action validation for run/proxy calls is implicit.	4 / 5
Progressive Disclosure	The body is organized into clear, mostly well-placed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to delegate to; it is not 5 because the skill exceeds 50 lines and some material (the full proxy flag table, popular actions) could be split out, leaving minor organization gaps.	4 / 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 is solid and well-formed: third-person, concise, with both a what and an explicit Use-when clause tied to a named product. Its weakness is generic action verbs and trigger phrases that lack the concrete, distinctive vocabulary users would actually say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Encore-specific operations (e.g., 'Deploy services, inspect infrastructure, and trigger Encore APIs').

Add natural trigger phrases and synonyms users would say (e.g., 'Use when the user wants to deploy or query an Encore app, inspect Encore logs, or call Encore endpoints').

Include concrete trigger nouns/file types or Encore concepts to lift distinctiveness above the generic 'Encore data' phrasing.

Dimension	Reasoning	Score
Specificity	The description names the domain (Encore) and a few actions — 'Manage data, records, and automate workflows' — but the verbs are generic rather than concrete operations, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor; it is above score 2 because multiple actions are listed, but below 4 since none are specific.	3 / 5
Completeness	It answers 'what' ('Encore integration. Manage data, records, and automate workflows') and 'when' with an explicit 'Use when the user wants to interact with Encore data' clause; the when-present cap at 3 does not apply, but the trigger phrase is generic so it stops short of the fully concrete level-5 phrasing.	4 / 5
Trigger Term Quality	It surfaces some relevant keywords ('Encore', 'data', 'records', 'workflows', 'interact with Encore data') but misses common variations or synonyms users would naturally say, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the specific Encore product gives it a clear niche with low overlap risk, matching 'mostly distinct; minor overlap risk'; it is not 5 because the trigger phrases themselves are generic ('Encore data') rather than distinctive operations.	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/encore/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.