CtrlK
BlogDocsLog inGet started
Tessl Logo

ecologi

Ecologi integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Ecologi 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

Fix and improve this skill with Tessl

tessl review fix ./skills/ecologi/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable with a well-sequenced, validated workflow and copy-paste commands. The only real gap is minor conciseness padding and the lack of any progressive-disclosure file split for the action reference.

DimensionReasoningScore

Conciseness

Mostly lean commands and tables with minor trimmable padding ("so you can focus on the integration logic rather than auth plumbing") and a brief opening paragraph explaining what Ecologi is.

4 / 5

Actionability

Copy-paste ready commands throughout (login, connection ensure, action list/run, request) with explicit flags and a Popular actions table covering common cases.

5 / 5

Workflow Clarity

Clear install→login→ensure→wait→search→run sequence with explicit state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops (re-poll after the user completes an action).

5 / 5

Progressive Disclosure

No bundle files exist; the self-contained body is well-sectioned with a reasonably placed inline Popular actions table, but at ~150 lines it does not qualify for the under-50-line simple-skill exception.

4 / 5

Total

18

/

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.

The description answers both what and when and is anchored to a distinct platform, but its trigger terms are thin and the "when" clause is generic. Listing more natural user phrases (carbon offset, trees, climate impact) would lift the weaker dimensions.

Suggestions

Add natural trigger keywords users actually say, e.g. "Use when the user wants to offset carbon footprint, plant trees, or check Ecologi climate impact."

Replace the generic "Manage… and more" with concrete Ecologi actions (get impact statistics, purchase trees, purchase carbon avoidance) to improve specificity.

Align the entity list with Ecologi's real features — the current Persons/Deals/Leads nouns read as a CRM skill, risking mismatched expectations.

DimensionReasoningScore

Specificity

Lists several concrete entity types ("Persons, Organizations, Deals, Leads, Projects, Activities"), but the repeated generic verb "Manage… and more" keeps it from comprehensive distinct actions.

4 / 5

Completeness

Both "what" (Ecologi integration, manage entities) and an explicit "when" ("Use when the user wants to interact with Ecologi data") are present, though the trigger phrase is generic.

4 / 5

Trigger Term Quality

Only the brand keyword "Ecologi" / "Ecologi data" appears; natural synonyms users would say (carbon offset, trees, climate, sustainability) are missing.

3 / 5

Distinctiveness Conflict Risk

Names a specific platform ("Ecologi integration") giving it a clear niche with minimal conflict risk against other skills.

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.