Name: faros
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

faros

Faros integration. Manage Organizations. Use when the user wants to interact with Faros data.

Quality

58%

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

Quality

Content

63%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 action-oriented with executable membrane commands and a solid connection-readiness workflow including validation checkpoints. It is held back by background padding and a large inlined actions table that would benefit from progressive disclosure into a separate reference.

Suggestions

Trim the introductory 'Faros is a data platform...' paragraph and the Faros AI Query/Response definitions, which restate concepts Claude already knows.

Move the 'Popular actions' table into a references file (e.g. actions.md) and link to it from SKILL.md.

Fix the step numbering (label Step 1/1a and Step 2) so cross-references like 'skip to Step 2' resolve clearly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary background ('Faros is a data platform for engineering leaders...') and definitional padding (Faros AI Query/Response) that Claude does not need.	3 / 5
Actionability	Provides concrete, copy-paste-ready membrane commands with flags and JSON examples covering install, auth, connection, action listing/running, and proxying, with only minor placeholder gaps.	4 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with explicit state-based validation and feedback loops for connection readiness, though step numbering is inconsistent ('1b', referenced 'Step 2') and there is no validation after running actions.	4 / 5
Progressive Disclosure	Well-organized into headed sections, but no bundle files exist and the large 20-row 'Popular actions' table and proxy-flag table are bulk reference content inlined in SKILL.md that could be split into a reference file.	3 / 5
	Total	14 / 20 Passed

Description

53%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 has an explicit Use-when clause and names a specific product, but undersells capabilities with a single generic action and a vague 'what' statement. It is distinguishable yet thin on concrete actions and natural trigger synonyms.

Suggestions

Replace 'Manage Organizations' with the broader set of concrete actions the skill supports (e.g., list/run graphs, accounts, webhooks, named queries, secrets).

Add natural trigger synonyms and phrasings a user would actually say, beyond just 'Faros data'.

Sharpen the 'what' to state concretely what the integration does rather than 'Faros integration'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Faros integration') and one concrete action ('Manage Organizations'), but the action is generic and the body reveals ~20 actions the description ignores, so coverage is not comprehensive.	3 / 5
Completeness	The 'what' is vague ('Faros integration' plus a single narrow action) and the explicit 'when' ('Use when the user wants to interact with Faros data') is generic, so both are present but neither is strong.	3 / 5
Trigger Term Quality	Includes the relevant term 'Faros data' in the Use-when clause, but lacks common variations or synonyms a user might naturally say beyond the product name.	3 / 5
Distinctiveness Conflict Risk	Faros is a specific named platform with a distinct trigger ('Faros data'), giving it a clear niche with only minor overlap risk against other data-integration 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/faros/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.