CtrlK
BlogDocsLog inGet started
Tessl Logo

little-green-light

Little Green Light integration. Manage Organizations, Funds, Campaigns, Appeals, Events, Tasks and more. Use when the user wants to interact with Little Green Light data.

61

Quality

73%

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/little-green-light/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable integration skill body with concrete commands and a clear connection-readiness workflow. Validation checkpoints on action results and some structural tightening would push it higher.

Suggestions

Add explicit validation after running actions and proxy requests, e.g. check the `output`/`error` field and retry or surface the error before proceeding.

Dedupe the 'action list' command between 'Searching for actions' and 'Popular actions', keeping a single canonical example.

Group the long flat entity overview (Constituents, Gifts, Reports, etc.) into a few labeled categories so it scans faster.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands and a flag reference table, avoiding basic-concept padding; the long flat entity overview and a near-duplicate 'action list' command in 'Popular actions' could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready bash commands (login, connection ensure, action list/run, request) with flags explained, covering common cases; it stops short of showing how to parse the --json output.

4 / 5

Workflow Clarity

The connection-readiness flow is well sequenced with polling and state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but action-running and proxy paths lack explicit verification checkpoints for results or errors.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is organized with clear section headers and an overview, though the flat entity list could be grouped for cleaner navigation.

4 / 5

Total

16

/

20

Passed

Description

71%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 focused, third-person description that names the product and lists concrete entities with an explicit use-when clause. Trigger phrasing and action verbs could be richer to lift it from good to excellent.

Suggestions

Replace the generic verb 'Manage' with concrete operations (e.g., 'Create, update, query, and report on Organizations, Funds, Campaigns...').

Add natural trigger variations users would say, such as 'donations', 'donor records', or 'fundraising data', beyond the product name alone.

Tighten 'Tasks and more' into a bounded list so the capability coverage reads as comprehensive rather than open-ended.

DimensionReasoningScore

Specificity

The description lists several specific entities ('Organizations, Funds, Campaigns, Appeals, Events, Tasks and more'), but the verb 'Manage' is generic rather than naming concrete operations like create/update/query.

4 / 5

Completeness

Both a clear 'what' (manage a named set of entities) and an explicit 'Use when the user wants to interact with Little Green Light data' clause are present; the 'when' could name more concrete trigger phrases.

4 / 5

Trigger Term Quality

It includes the product name 'Little Green Light' and 'interact with Little Green Light data', but lacks common natural synonyms or variations a user would actually phrase.

3 / 5

Distinctiveness Conflict Risk

'Little Green Light' is a named, niche product, giving it distinct triggers and minimal risk of firing for the wrong skill.

5 / 5

Total

16

/

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.