Name: instatus
Rating: 56.8 (1 reviews)
Author: membranedev

instatus

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/instatus/SKILL.md

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 body is a mostly lean, executable guide with a genuine connection-state feedback loop, undermined by an unnecessary intro paragraph and inconsistent step numbering. No bundle files exist, so all content is appropriately inline and well-sectioned.

Suggestions

Cut the opening "Instatus is a status page platform..." background paragraph; Claude does not need the business rationale.

Fix the step numbering: define an explicit "Step 1/Step 2" structure or relabel the orphan "1b" and the undefined "Step 2" references.

Add one complete proxy example with method, data, and a real endpoint to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Instatus is and why companies use it ("helps companies communicate incidents... improve transparency and build trust") is background Claude does not need, plus promotional lines like "so you can focus on the integration logic rather than auth plumbing".	3 / 5
Actionability	Copy-paste-ready commands cover install, login, connect, poll, search, run, and proxy with an options table, but examples lean on placeholders (CONNECTION_ID, <id>) and the proxy section lacks one complete annotated example.	4 / 5
Workflow Clarity	There is a clear install→auth→connect→discover→run sequence with an explicit poll/retry feedback loop for connection readiness, but step numbering is broken (references to "Step 2" with no Step 2 header, an orphan "1b" subsection).	4 / 5
Progressive Disclosure	Clean section headers make the single-file skill navigable, and inlined content (lifecycle states, options table) is reasonable with no bundle files present, but nothing is split into references so it stays just below a 5.	4 / 5
	Total	15 / 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 answers both what and when and is anchored to a specific product, but its action vocabulary is generic rather than tied to Instatus's actual capabilities. Tightening the triggers to concrete Instatus concepts (incidents, status pages, components) would raise it.

Suggestions

Replace generic actions ("Manage data, records") with concrete Instatus capabilities such as incidents, components, metrics, and subscribers.

Add natural trigger phrases users would say, e.g. "Use when the user mentions status pages, incidents, maintenance windows, or subscriber notifications."

Mention the status-page/incident-management domain explicitly so it is distinguishable from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and several actions, but the actions are generic rather than concrete Instatus-specific capabilities (incidents, components, metrics, subscribers).	3 / 5
Completeness	It states both what it does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Instatus data"), but the trigger is generic rather than concrete phrases.	4 / 5
Trigger Term Quality	"Instatus integration" and "interact with Instatus data" include the core product keyword, but miss common natural variations a user would say (status page, incidents, maintenance, downtime).	3 / 5
Distinctiveness Conflict Risk	Naming the specific Instatus product gives it a clear niche, but the generic verbs ("Manage data, records, and automate workflows") create minor overlap risk with other integration skills absent the product name.	4 / 5
	Total	14 / 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/instatus/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.