Name: phos
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

phos

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

Quality

75%

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

Quality

Content

88%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, highly actionable CLI integration guide with clear sequenced workflows and explicit validation checkpoints via connection-state handling. It is efficient and copy-paste ready, with only minor organizational and conciseness tweaks needed.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, built around executable commands and Membrane-specific behavior Claude would not know, with only minor editorial padding like 'so you can focus on the integration logic rather than auth plumbing', matching the score-4 anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for every stage (login, connection ensure, action list/run, request) plus a concrete flag table, fully covering the common cases as in the score-5 anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced (install, auth, ensure, poll) with explicit state-based validation (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop instructing re-polling after the user acts, matching the score-5 anchor.	5 / 5
Progressive Disclosure	No bundle files exist and the content is appropriately self-contained with clear section headers, but at ~150 lines a few sections (e.g. the redundant 'Popular actions' vs 'Searching for actions') could be reorganized, matching score 4.	4 / 5
	Total	18 / 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 covers both what and when with an explicit 'Use when' trigger tied to the named Phos app, but its action list is generic and the trigger phrasing lacks synonyms. It is solid but could be sharper with more concrete capabilities and broader trigger terms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Phos capabilities such as querying meeting transcripts, listing participants, or running cost-optimization actions.

Broaden the trigger clause to include natural variations, e.g. 'Use when the user wants to query, search, or automate workflows against Phos data or meeting/transcription records.'

Tie triggers to observable user intent ('track or optimize cloud spend', 'pull Phos records') to reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the Phos domain and a couple of actions ('Manage data, records, and automate workflows'), but the listed actions are fairly generic rather than concrete and comprehensive, matching the score-3 anchor of domain plus 1-2 actions with gaps.	3 / 5
Completeness	It states both what ('Phos integration. Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Phos data'), though the when clause is somewhat narrow, matching the score-4 anchor.	4 / 5
Trigger Term Quality	The only natural trigger phrase is 'interact with Phos data', which mirrors the score-3 example 'Works with PDF files' — relevant but missing common variations or synonyms of the trigger.	3 / 5
Distinctiveness Conflict Risk	Phos is a named application giving a clear niche, but the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap risk with other integration skills, matching score 4 rather than 5.	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/phos/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.