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

Blog Docs Log in Get started

softr

Softr integration. Manage Applications. Use when the user wants to interact with Softr 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/softr/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 body is a well-structured, highly actionable CLI guide with executable commands and a clear connection-state feedback loop. Its main gaps are a broken 'Step 2' cross-reference, no validation guidance for destructive proxy calls, and a little trimmable marketing prose.

Suggestions

Fix the dangling step references: label an explicit 'Step 1' / 'Step 2' or replace "skip to Step 2" with a concrete section anchor.

Add a brief validation/verification note for destructive proxy methods (POST/PUT/DELETE), e.g., confirming the target before non-GET requests.

Trim non-essential prose such as the opening Softr marketecture sentence and the 'focus on integration logic rather than auth plumbing' commentary.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, command-driven content with only minor trimmable fluff such as the opening marketecture sentence ("It's used by entrepreneurs, small businesses...") and "so you can focus on the integration logic rather than auth plumbing". Not a 5 because those few explanatory sentences earn no token; not a 3 because the bulk is tight and actionable.	4 / 5
Actionability	Provides copy-paste-ready commands covering install, login, connection, polling, action search/run, and proxy requests, plus a flag table for proxy options. Not below 5 because the examples are executable and cover the common cases with concrete placeholders.	5 / 5
Workflow Clarity	Clear install → authenticate → connect → poll → search → run sequence with an explicit state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/error) for error recovery. Not a 5 because it references a "Step 2" that is never labeled and offers no validation guidance for destructive proxy methods (POST/PUT/DELETE); not a 3 because real checkpoints and a re-poll loop are present.	4 / 5
Progressive Disclosure	Well-organized into clear headed sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files to navigate. Not a 5 because the skill exceeds 50 lines and the over-50 simple-skill exception does not apply, yet all content remains inline with no one-level-deep references split out.	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 a clear Softr-specific niche that avoids conflict risk. Its main weakness is a generic 'what' ("Manage Applications") that lacks specific concrete capabilities.

Suggestions

Expand the 'what' with concrete Softr capabilities (e.g., list specific actions like managing users, pages, or app data) instead of the generic "Manage Applications".

Add natural trigger synonyms or variants users might say (e.g., "Softr apps", "Softr users", "Softr pages") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Softr integration") and offers one to two action phrases ("Manage Applications", "interact with Softr data"), but the actions are generic and not comprehensive. Not a 4 because it does not list several specific concrete actions; not a 2 because it does name more than a single minimal action.	3 / 5
Completeness	States both the what ("Softr integration. Manage Applications.") and an explicit when ("Use when the user wants to interact with Softr data."). Not a 5 because the 'what' is thin and generic rather than a comprehensive list of concrete actions; not a 3 because the 'when' is explicit, not merely implied.	4 / 5
Trigger Term Quality	Includes natural terms a user would say — "Softr", "Applications", "Softr data" — with a concrete "Use when the user wants to interact with Softr data" trigger phrase. Not a 5 because coverage lacks synonyms or file/extension-style variations; not a 3 because the keyword set is genuinely good rather than sparse.	4 / 5
Distinctiveness Conflict Risk	Targets a named platform ("Softr") with a distinct trigger ("Use when the user wants to interact with Softr data"), giving it a clear niche with minimal conflict risk. Not below 5 because no other generic skill would claim this trigger.	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/softr/SKILL.md
Commit: f484c82

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