CtrlK
BlogDocsLog inGet started
Tessl Logo

firstup

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

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/firstup/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 content is a highly actionable, command-driven integration guide with a sound connection-state feedback loop and clean sectioning. Its main weaknesses are minor prose padding, slight section redundancy, and absent post-action verification.

Suggestions

Tighten the introductory prose and the sparse "Firstup Overview" bullet list to remove padding that does not aid execution.

Add a brief verification step after running actions or proxy requests (e.g. inspect the response `output`/status and confirm before reporting success) to strengthen the workflow's feedback loop.

Merge the "Searching for actions" and "Popular actions" sections, which both demonstrate `action list --intent`, to remove redundancy.

DimensionReasoningScore

Conciseness

The body is mostly lean commands with brief explanations, though a few prose passages ("Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing") and the thin bullet Overview could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready commands throughout (npm install, membrane login incl. headless flow, connection ensure, polling, action list/run, request proxy with a full flag table) covering the common integration cases.

5 / 5

Workflow Clarity

A clear install -> auth -> connect -> poll -> search -> run sequence exists with an explicit feedback loop (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but step labels are loose ("Step 2" referenced without a labeled 1a) and there is no post-action verification.

4 / 5

Progressive Disclosure

As a single well-sectioned file with no bundle files, content is appropriately organized for its scope; minor redundancy between "Searching for actions" and "Popular actions" keeps it just below a fully clean overview.

4 / 5

Total

17

/

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 clearly identifies the Firstup niche and includes an explicit use-when clause, but its action verbs are generic and the trigger phrasing is narrow. It is solid and distinct, just not comprehensive.

Suggestions

Replace generic verbs with concrete actions, e.g. "List, create, and update Firstup users, content, and segments" to raise specificity.

Expand the trigger clause with natural variations, e.g. "Use when the user mentions Firstup, wants to send push notifications or manage segments, or automate Firstup workflows."

DimensionReasoningScore

Specificity

Names the Firstup domain and several action categories ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, landing between the minimal-actions anchor (2) and a comprehensive list.

3 / 5

Completeness

States both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Firstup data"), but the when clause is a single generic trigger rather than varied concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes the distinctive product name "Firstup" and terms like "data", "records", and "workflows", but lacks common variations or synonyms a user might naturally say, matching the some-relevant-keywords anchor.

3 / 5

Distinctiveness Conflict Risk

Tied to the unique named product "Firstup", giving it a clear niche and low conflict risk, though the generic action phrasing leaves minor overlap with other data-integration 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.