CtrlK
BlogDocsLog inGet started
Tessl Logo

amazon-cognito

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

53

Quality

60%

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/amazon-cognito/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 executable CLI commands and a clear state-driven connection workflow, but it spends tokens explaining Cognito basics and inlines content that a reference file would better absorb.

Suggestions

Trim the introductory paragraph explaining what Amazon Cognito is; assume Claude's knowledge and keep only Membrane-specific integration details.

Move the entity overview list and detailed action/connection reference into a references file (e.g. references/actions.md) and link to it one level deep from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Most CLI commands and code blocks are lean and earn their place, but the opening "Amazon Cognito is a service that lets developers add user sign-up, sign-in..." explains a concept Claude already knows and there is some padded framing around Membrane.

3 / 5

Actionability

It provides concrete executable commands throughout (npm install, membrane login, connection ensure, action run, request) with mostly copy-paste-ready examples, with only minor gaps like the CONNECTION_ID placeholder.

4 / 5

Workflow Clarity

The connection flow is clearly sequenced with state-based polling (BUILDING -> READY / CLIENT_ACTION_REQUIRED) and an explicit feedback loop (poll again after the user acts), plus error-state handling; minor validation gaps remain.

4 / 5

Progressive Disclosure

No bundle files exist and nothing is split into referenced files; the ~160-line body is section-organized but inlines reference-like content (the 15-entity overview list and connection/action details) without one-level-deep signaled references.

3 / 5

Total

14

/

20

Passed

Description

57%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 explicitly answers both what and when and is anchored to a specific named service, but its capability statement is generic ('manage data, records, and automate workflows') and lacks Cognito-specific trigger terms.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Cognito capabilities such as managing user pools, identity pools, users, groups, tokens, and MFA.

Expand trigger terms to include natural phrases users say, e.g. 'Use when the user wants to manage Amazon Cognito users, user pools, identity pools, authentication, or sign-in flows.'

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Amazon Cognito domain but the actions are minimal and generic, with no concrete Cognito-specific operations (users, user pools, auth, tokens).

2 / 5

Completeness

Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Amazon Cognito data") are present; the 'when' is explicit though the 'what' is somewhat generic.

4 / 5

Trigger Term Quality

It includes the trigger phrase "Use when the user wants to interact with Amazon Cognito data" and the service name, but misses natural synonyms users would say (authentication, sign-in, user pool, identity pool).

3 / 5

Distinctiveness Conflict Risk

The named AWS service ("Amazon Cognito") gives it a clear niche with mostly distinct triggers, with only minor overlap risk against generic AWS or data-management skills.

4 / 5

Total

13

/

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.