CtrlK
BlogDocsLog inGet started
Tessl Logo

porter

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

64

Quality

77%

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

Quality

Content

92%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 highly actionable with executable commands, a clear sequenced workflow, and an explicit state-polling feedback loop for the connection lifecycle. Minor conciseness gains are available by trimming a few explanatory asides.

DimensionReasoningScore

Conciseness

The body is mostly efficient and command-focused, with only minor over-explanation ("Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing") that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready, executable commands for install, auth, connection, polling, action search/run, and proxying, plus a flag reference table covering the common cases.

5 / 5

Workflow Clarity

Sequences install -> auth -> connect -> poll -> search -> run with an explicit state-based feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-poll instructions for error recovery.

5 / 5

Progressive Disclosure

A single self-contained file with clear, well-organized section headers and no bundle files, so the simple-skill exception for well-organized content applies.

5 / 5

Total

19

/

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 the skill does and when to use it with an explicit trigger clause, but relies on generic verbs (manage, automate) rather than concrete Porter-specific actions. Naming the Porter app keeps conflict risk low.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Porter capabilities such as deploying apps, viewing job outputs, or checking credits.

Add natural trigger synonyms and file/URL cues (e.g. 'deployments', 'jobs', 'porter.run') so users phrasing the request differently still match.

Tighten the 'when' clause to specific intents (e.g. 'Use when the user wants to deploy, inspect, or manage Porter applications').

DimensionReasoningScore

Specificity

Names the Porter domain and a few actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

States both a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ("Use when the user wants to interact with Porter data"), though the trigger could be more specific, matching the 'has both what and when' anchor.

4 / 5

Trigger Term Quality

Includes relevant keywords (Porter, data, records, workflows) and one natural phrase ("interact with Porter data"), but misses common synonyms and variations users might say, fitting the 'some relevant keywords' anchor.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Porter app gives a clear niche with minimal conflict risk, though the generic 'data/records/workflows' actions retain minor overlap with broad data 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.