CtrlK
BlogDocsLog inGet started
Tessl Logo

polygon

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

60

Quality

71%

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/polygon/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a tight, executable integration guide with a well-sequenced connection workflow and explicit state-based validation feedback. The only weakness is minor over-explanation of background concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly executable bash commands with brief framing, though lines explaining what Polygon/Membrane is and what auth plumbing does are mild over-explanation Claude largely already knows.

4 / 5

Actionability

Copy-paste-ready commands cover install, login, connection, action search/run, and proxying, with concrete parameter and JSON-input examples for the common cases.

5 / 5

Workflow Clarity

Connecting-to-Polygon is a clear sequence with an explicit polling checkpoint and state-driven feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) plus re-poll after user action.

5 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into clear sections (install, auth, connect, search, run, proxy, best practices), which per the simple-skill guidance earns a 5.

5 / 5

Total

19

/

20

Passed

Description

58%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 trigger and names the Polygon domain plus a concrete action, but it is thin on the breadth of capabilities and natural trigger synonyms. It is competent but not comprehensive.

Suggestions

Expand specificity by listing the concrete operations available (e.g. query market data, list tickers, manage documents) instead of only "Manage Organizations".

Add natural trigger keywords and synonyms users would say, such as "ticker", "market status", "OHLC bars", or "Polygon.io API".

Tighten the when-clause to name the specific scenarios (e.g. retrieving stock/crypto market data or managing Polygon workspaces) rather than the generic "interact with Polygon data".

DimensionReasoningScore

Specificity

"Manage Organizations" names one concrete action within the Polygon domain but coverage is minimal rather than comprehensive, matching the domain-plus-1-2-actions anchor.

3 / 5

Completeness

It gives a clear what ("Manage Organizations") and an explicit "Use when the user wants to interact with Polygon data" trigger, though the when is somewhat generic.

4 / 5

Trigger Term Quality

"Polygon data" and "interact with Polygon data" provide a couple relevant terms but miss natural synonyms and file/endpoint extensions users would say.

3 / 5

Distinctiveness Conflict Risk

"Polygon integration" / "Polygon data" carves a fairly distinct niche with minor overlap risk against generic data-management skills.

4 / 5

Total

14

/

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.