CtrlK
BlogDocsLog inGet started
Tessl Logo

thoughtful-gpt

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

55

Quality

62%

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

Quality

Content

67%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 well-structured, actionable guide to driving Thoughtful GPT via the Membrane CLI, with executable commands and a connection-readiness feedback loop. Its main weakness is light padding in the intro and a few undefined step references.

Suggestions

Trim the introductory marketing paragraph ('AI-powered writing assistant...marketers, bloggers') since it does not aid execution.

Resolve the dangling 'Step 2' reference by explicitly numbering the post-connection steps (search actions → run / proxy).

Flesh out one fully-worked action example with concrete QUERY and CONNECTION_ID values so the run path is end-to-end copy-pasteable.

DimensionReasoningScore

Conciseness

The body is mostly efficient CLI commands, but the opening paragraph ('AI-powered writing assistant...used by marketers, bloggers') and phrasing like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude could infer, fitting the 'mostly efficient with some unnecessary explanation' anchor.

3 / 5

Actionability

It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and request with flags and JSON examples, fitting 'mostly executable guidance with minor gaps'; a few examples use placeholders like QUERY/CONNECTION_ID rather than a fully worked case.

4 / 5

Workflow Clarity

There is a clear install→authenticate→connect→search→run sequence with a polling feedback loop and state checks (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), matching the 'clear sequence with most checkpoints' anchor; the dangling 'Step 2' reference and undefined step numbering are minor gaps.

4 / 5

Progressive Disclosure

The single SKILL.md is organized into well-labeled sections (Overview, Working with, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references and no bundle files needed, fitting 'good structure, minor organization gaps'; some inline reference-like detail keeps it from a 5.

4 / 5

Total

15

/

20

Passed

Description

57%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 includes an explicit Use-when trigger and a distinct product name, but its capability list relies on generic verbs ('manage data, records, automate workflows') rather than concrete actions. It is functional but underspecified.

Suggestions

Replace generic verbs with concrete actions the integration performs (e.g., 'create and retrieve Thoughts, run Plans, query Knowledge Sources').

Add natural synonyms and entity terms users might say (e.g., 'Thoughtful GPT thoughts, plans, sessions') to broaden trigger coverage.

Tighten the 'what' so it reads as a capability list tied to the API's actual objects, not abstract workflow language.

DimensionReasoningScore

Specificity

The description names the domain (Thoughtful GPT) but its actions are generic verbs — 'Manage data, records, and automate workflows' — rather than concrete capabilities, matching the anchor that names the domain with minimal/generic actions.

2 / 5

Completeness

It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Thoughtful GPT data'), matching the anchor where both are present though the 'what' could be more specific; the explicit Use-when clause lifts it above 3.

4 / 5

Trigger Term Quality

It surfaces the product name and a usable trigger ('Use when the user wants to interact with Thoughtful GPT data') but lacks synonyms or file/extension variations, fitting the anchor with some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

The distinctive product name 'Thoughtful GPT' anchors the trigger and limits overlap with other skills, fitting the 'mostly distinct; minor overlap risk' anchor; the generic action verbs keep it from a 5.

4 / 5

Total

13

/

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.