Name: streak
Rating: 64.8 (1 reviews)
Author: membranedev

streak

Streak integration. Manage Persons, Organizations, Deals, Pipelines, Users, Roles. Use when the user wants to interact with Streak data.

Quality

78%

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

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 content is highly actionable with copy-paste-ready CLI commands and a clear connection workflow that includes polling and error-recovery feedback loops. Its weaknesses are minor: some redundant/over-explained passages and an undefined "Step 2" reference that slightly weaken conciseness and workflow clarity.

Suggestions

Define or remove the dangling "skip to Step 2" reference so the workflow sequence is unambiguous.

De-duplicate the action-list command (shown in both "Searching for actions" and "Popular actions") and trim explanatory padding like the auth-plumbing aside.

Consider moving the detailed clientAction state-handling and proxy-flags table into a reference file to better separate overview from reference material.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with brief framing, but includes minor over-explanation ("Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing") and redundancy (action list --intent=QUERY is shown in both "Searching for actions" and "Popular actions"), keeping it just below lean/efficient-5.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, poll, action list/run, proxy) plus a full proxy-flags table, with concrete placeholders that make the guidance fully executable.	5 / 5
Workflow Clarity	The connection flow has a clear install→auth→ensure→poll→state-check sequence with a feedback loop (CLIENT_ACTION_REQUIRED → user acts → poll again), but "skip to Step 2" references an undefined Step 2 and there is no explicit validation after running actions, leaving minor gaps versus the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single well-sectioned SKILL.md (~156 lines) with clear headers and no nested references, but content like the detailed clientAction state-handling and proxy-flags table could justify a separate reference file, so it is not a 5.	4 / 5
	Total	17 / 20 Passed

Description

73%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 cleanly states what the skill does and when to use it, with strong distinctiveness from a named CRM niche. Its main weakness is the generic verb "Manage" and a single, non-enumerated trigger clause that leave specificity and completeness just short of the top anchors.

Suggestions

Replace the generic verb "Manage" with concrete operations, e.g. "Create, update, search, and delete Persons, Organizations, Deals, Pipelines, Users, and Roles."

Expand the "Use when" clause with concrete trigger phrases, e.g. "Use when the user wants to manage Streak deals, pipelines, contacts, or boxes, or interact with Streak data in Gmail."

Add common synonyms users say (contacts, leads, boxes) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Pipelines, Users, Roles" names the domain and several concrete entities, but the single generic verb "Manage" does not enumerate distinct concrete actions like extract/fill/convert, keeping it just below the 4 anchor.	3 / 5
Completeness	It has both a clear "what" ("Streak integration. Manage Persons, Organizations, Deals, Pipelines, Users, Roles.") and an explicit "when" ("Use when the user wants to interact with Streak data."), but the "when" is a single generic clause rather than the rich concrete trigger phrases seen in the 5 anchor.	4 / 5
Trigger Term Quality	Natural entity terms ("Persons, Organizations, Deals, Pipelines, Users, Roles" and "Streak data") give good keyword coverage a user would say, but common synonyms like contacts, leads, or boxes are missing, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	"Streak integration" tied to Streak-specific entities is a clear, named niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/streak/SKILL.md
Commit: f484c82

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