CtrlK
BlogDocsLog inGet started
Tessl Logo

resource-guru

Resource Guru integration. Manage Persons, Projects, Clients, Bookings. Use when the user wants to interact with Resource Guru data.

66

Quality

80%

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

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.

A highly actionable CLI integration guide with executable commands, a clear connection-readiness workflow, and a useful state-handling feedback loop. Its weaknesses are minor verbosity in the intro, a missing verification loop on the action-execution path, and slightly inconsistent step numbering.

Suggestions

Trim the opening paragraph ('Resource Guru is a resource scheduling tool...') and the 'auth plumbing' aside to tighten conciseness.

Add an explicit verify/retry step after 'membrane action run' (e.g. check the `output`/error field and re-run or fall back to the proxy on failure) to strengthen the action-execution workflow.

Fix the step numbering so '1b' and 'Step 2' have matching labelled anchors (e.g. label the ensure step '1a') for clearer navigation.

DimensionReasoningScore

Conciseness

Mostly a lean, command-driven reference with executable blocks. Not 5 because of minor padding such as the opening product blurb and 'auth plumbing' phrasing that could be trimmed.

4 / 5

Actionability

Copy-paste-ready commands throughout (install, login, connection ensure, poll, action list/run, request) with clearly marked placeholders covering the common cases.

5 / 5

Workflow Clarity

Clear install->auth->connect->search->run sequence with a polling feedback loop and state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED). Not 5 because the action-run path lacks an explicit verify/retry loop and there is no checklist.

4 / 5

Progressive Disclosure

Well-organized sections in a single-file CLI guide that is appropriately kept together (no bundle files exist). Not 5 because the '1b'/'Step 2' numbering is inconsistently labeled and there are no navigation aids.

4 / 5

Total

17

/

20

Passed

Description

78%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.

A clear, specific description that names the target app and its core entities, with an explicit 'Use when' trigger clause. The main weakness is the generic 'Manage' verb and the broad 'when' phrasing, which limit specificity and completeness from reaching the top level.

Suggestions

Replace the single 'Manage' verb with concrete CRUD-style actions (e.g. 'Create, update, and list Persons, Projects, Clients, and Bookings') to raise specificity.

Expand the 'Use when' clause with concrete trigger phrases (e.g. 'Use when the user mentions bookings, resource scheduling, or managing clients and projects in Resource Guru').

Add common synonyms such as 'people', 'scheduling', and 'resources' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete entities ('Persons, Projects, Clients, Bookings') under a single 'Manage' verb. Not 5 because the verb is generic with no CRUD-level granularity; not 3 because it names more than 1-2 concrete items.

4 / 5

Completeness

Answers both what ('Manage Persons, Projects, Clients, Bookings') and when ('Use when the user wants to interact with Resource Guru data'). Not 5 because the 'when' is generic rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural domain terms ('Resource Guru', 'Persons, Projects, Clients, Bookings') are present. Not 5 because synonyms like 'scheduling', 'resources', and 'people' are missing.

4 / 5

Distinctiveness Conflict Risk

Names a specific SaaS tool ('Resource Guru integration') with a clear niche and distinct triggers, giving minimal conflict risk with other skills.

5 / 5

Total

17

/

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.