CtrlK
BlogDocsLog inGet started
Tessl Logo

remove-demo-limits

Removes Open Harness hosted demo restrictions from a fork. Use when a maintainer wants to remove managed-template trial caps, hosted deployment gating, or "deploy your own" limits. Triggers on "remove demo limits", "remove trial limits", "remove hosted restrictions", "open this up for my fork", "remove managed template restrictions".

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, well-structured, and actionable with concrete file paths, grep targets, and a verification command. The main gaps are a missing code example of the guards to remove and an incomplete fix-and-retry feedback loop in verification.

Suggestions

Add a short code snippet showing an example managed-template guard (e.g. an `isManagedTemplateTrialUser` check) and what removing it looks like, so the action is copy-paste concrete rather than described.

Extend the Verification section with an explicit feedback loop: if `bun run ci` fails on a test your changes touched, fix the edit and re-run until green, in addition to separating out pre-existing failures.

Clarify step 3's branch ('Delete ... if it becomes unused; otherwise simplify') with a one-line check for how to determine unused (e.g. grep for remaining importers) so the decision is mechanical.

DimensionReasoningScore

Conciseness

The body is lean and efficient: no over-explanation of concepts Claude already knows, just the single useful fact ('This repo uses Bun') plus concrete file paths, identifiers, and directives. Every token earns its place.

5 / 5

Actionability

Highly actionable guidance — exact files to read, identifiers/strings to grep, six numbered changes, and a concrete verification command (`bun run ci`) — but as an instruction-only skill it includes no example of the actual guard code to remove, leaving a minor gap.

4 / 5

Workflow Clarity

A clear Inspect → Required changes → Verification → Output sequence with a validation checkpoint (`bun run ci`), but the error-recovery loop only addresses pre-existing failures ('say that clearly and separate it') without an explicit fix-and-re-run step for failures introduced by the edits.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clearly headed sections (Goal, Inspect first, Required changes, Verification, Output); per the simple-skills note this earns a 5 on structure alone.

5 / 5

Total

18

/

20

Passed

Description

95%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 is strong: it explicitly answers both what and when, supplies natural trigger phrases with synonyms, and occupies a distinct niche. The only minor weakness is that the capability list is all variants of 'remove X' rather than a broader action vocabulary.

DimensionReasoningScore

Specificity

Names the domain ('Open Harness hosted demo restrictions from a fork') and several concrete restriction types to remove (trial caps, deployment gating, 'deploy your own' limits), but every action is a variant of 'remove X', leaving minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

Clearly states what it does ('Removes Open Harness hosted demo restrictions from a fork') and explicitly when to use it with concrete trigger phrases, matching the anchor for explicit what-and-when.

5 / 5

Trigger Term Quality

An explicit 'Triggers on' clause lists five natural phrases a maintainer would say ('remove demo limits', 'remove trial limits', 'open this up for my fork', etc.) with synonyms across demo/trial/hosted/managed-template wording.

5 / 5

Distinctiveness Conflict Risk

A narrow product-specific niche (Open Harness fork demo restrictions) with highly distinct triggers means minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Kiz8-Team/open-agents
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.