CtrlK
BlogDocsLog inGet started
Tessl Logo

phyllo

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

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/phyllo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, executable CLI usage guide with concrete commands and good workflow sequencing for connection setup. Minor improvements in step labeling and validation for destructive proxy calls would round it out.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with little padding; the only mild over-explanation is the opening "Phyllo is a data connectivity platform for the creator economy..." paragraph, which could be trimmed but is justified context for a niche platform.

4 / 5

Actionability

Copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action run, request) with --json flags and a concrete proxy-options table, fully covering the common cases an agent would execute.

5 / 5

Workflow Clarity

The connection workflow has explicit feedback loops (poll BUILDING -> handle CLIENT_ACTION_REQUIRED -> re-poll until READY), but the "skip to Step 2" reference points to an undefined step and destructive proxy operations (POST/DELETE) lack validation checkpoints, leaving minor gaps.

4 / 5

Progressive Disclosure

Content is well-organized under clear section headers (Overview, Install, Auth, Connecting, Searching, Actions, Proxy, Best practices) in a single self-contained file with no nested or buried references, though it is longer than the simple-skill threshold so it stops just short of a 5.

4 / 5

Total

17

/

20

Passed

Description

66%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 what and when and is clearly niche-specific to Phyllo, but its action verbs are generic and it lacks richer trigger-term coverage. Tightening the capability list and adding concrete scenarios would lift the weaker dimensions.

Suggestions

Replace generic verbs with concrete Phyllo operations (e.g., "Retrieve creator work platforms, identities, and engagement metrics") so the capability list is specific rather than "manage data, records, and automate workflows".

Expand the trigger clause with natural scenarios users actually say, e.g., "Use when the user wants to pull creator analytics, connect a creator account, or query engagement data from Phyllo."

Add file-format or endpoint synonyms where relevant (e.g., mentioning YouTube/TikTok/Instagram creator data) so the description surfaces more natural trigger terms.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Phyllo domain with a few actions, but the verbs are generic ("manage", "automate") rather than concrete operations, matching the 1-2 concrete-actions anchor without being comprehensive.

3 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Phyllo data"), but the trigger could be more explicit with concrete scenarios, matching the both-present-but-could-be-more-specific anchor.

4 / 5

Trigger Term Quality

"Use when the user wants to interact with Phyllo data" offers a relevant natural phrase but lacks common synonyms or scenario variations a user might say, sitting at the some-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

"Phyllo" is a distinct named platform with a clear niche and the trigger "interact with Phyllo data" is specific, giving minimal conflict risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.