Name: focalboard
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

focalboard

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

Quality

66%

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/focalboard/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 body is highly actionable with concrete, executable Membrane CLI commands and a solid connection-state workflow including a feedback loop. Its main weaknesses are marketing-toned padding and a broken step-numbering scheme that slightly obscures the workflow.

Suggestions

Trim the marketing-toned intro and auth commentary (e.g. 'so you can focus on the integration logic rather than auth plumbing') and remove the bare Focalboard Overview bullet list or expand it with real meaning.

Fix the incoherent step numbering ('1b' with no '1a', references to 'Step 2' that is not labeled) so the connection workflow sequence is unambiguous.

Either populate 'Popular actions' with the named common actions or rename the section to 'Discovering actions' so it matches its actual content.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the intro paragraph ('often compared to Asana or Trello... visual and collaborative manner') and phrases like 'so you can focus on the integration logic rather than auth plumbing' plus the bare Focalboard Overview bullet list are unnecessary padding that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (npm install, membrane login, connection ensure, action run, request) with a complete flags table, covering the common integration cases.	5 / 5
Workflow Clarity	The connect-then-poll-then-act sequence is clear with an explicit state-based feedback loop (CLIENT_ACTION_REQUIRED -> re-poll), but the 'skip to Step 2' and '1b' numbering is incoherent and verification of action results is only implicit ('result is in the output field').	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into clearly labeled sections with no nested references needed, though the 'Popular actions' section advertises a list but only shows a discovery command, a minor organization gap.	4 / 5
	Total	16 / 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 correctly pairs a what-and-when structure with an explicit product trigger, but its capability list is generic boilerplate rather than concrete Focalboard-specific actions. It is functional but would benefit from naming actual operations (boards, cards, blocks) users perform.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Focalboard operations such as 'create and update boards, cards, and blocks' to lift specificity.

Add natural trigger synonyms users might say, e.g. 'Focalboard boards, cards, or tasks' alongside file/URL references, to improve trigger-term coverage.

Tie the 'Use when' clause to concrete scenarios, e.g. 'Use when the user wants to create or update Focalboard boards, cards, or workflows.'

Dimension	Reasoning	Score
Specificity	It names the domain (Focalboard) but the listed actions — 'Manage data, records, and automate workflows' — are generic boilerplate rather than concrete operations, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	Both 'what' (Focalboard integration; manage data, records, workflows) and 'when' ('Use when the user wants to interact with Focalboard data') are present and explicit, but the 'what' is generic rather than concrete, so it stops short of a 5.	4 / 5
Trigger Term Quality	'Focalboard' is a strong natural product-name trigger, but the remaining keywords (data, records, workflows) are generic and lack common synonyms or file extensions, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The specific Focalboard product name gives it a clear niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing could overlap with other project-management skills.	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/focalboard/SKILL.md
Commit: f484c82

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