CtrlK
BlogDocsLog inGet started
Tessl Logo

amazon-alexa

Integracao completa com Amazon Alexa para criar skills de voz inteligentes, transformar Alexa em assistente com Claude como cerebro (projeto Auri) e integrar com AWS ecosystem (Lambda, DynamoDB, Polly, Transcribe, Lex, Smart Home).

51

Quality

56%

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

Quality

Content

47%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 clean, token-efficient overview page that correctly delegates detail to a real one-level reference file. However, the body itself carries no actionable procedure or sequenced workflow — everything hinges on the external guide — and the guide contains a dangling reference to a missing smart-home-api.md file.

Suggestions

Add a brief quick-start section in the body (e.g., the Auri architecture summary and the first 2-3 concrete setup steps) so the skill is actionable without immediately loading the full guide.

Include explicit validation checkpoints or a sequenced workflow outline in the body rather than only a blanket 'treat validation requirements as mandatory' directive.

Fix or remove the dangling references/smart-home-api.md link inside references/detailed-guide.md, since that file does not exist in the bundle.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows ("Read [the detailed guide](references/detailed-guide.md) before executing this skill"), though generic filler like "When you need specialized assistance with this domain" earns little and could be trimmed.

4 / 5

Actionability

The only concrete instruction is to read the reference file; the body contains no code, commands, or domain-specific steps — "Read [the detailed guide]... before executing this skill" is a high-level hint that delegates all executable guidance. It is not a 1 because the pointer is specific (exact path, when to load sections vs. fully), and not a 3 because no partial executable guidance exists in the body itself.

2 / 5

Workflow Clarity

Only a rough implicit sequence exists (read the guide, then execute) with no listed steps and no validation checkpoints in the body — validation is merely delegated via "Treat its safety, prerequisites, and validation requirements as mandatory". Not a 1 because the directive is coherent rather than incoherent.

2 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled, one-level-deep reference (references/detailed-guide.md, which exists and holds the 644-line procedure). Not a 5 because the guide itself dangles a reference to references/smart-home-api.md, which is not present in the bundle.

4 / 5

Total

12

/

20

Passed

Description

66%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 domain-specific description with strong niche identity and named AWS services, giving good trigger-term coverage and low conflict risk. Its main weakness is the complete absence of an explicit 'Use when...' trigger clause, leaving the 'when to use' question unanswered and capping completeness.

DimensionReasoningScore

Specificity

It lists several concrete actions — "criar skills de voz inteligentes", "transformar Alexa em assistente com Claude como cerebro", "integrar com AWS ecosystem" — plus seven named AWS services (Lambda, DynamoDB, Polly, Transcribe, Lex, Smart Home). Not a 5 because the framing "Integracao completa" keeps the actions at a fairly high level without comprehensive operational coverage.

4 / 5

Completeness

The 'what' is clear (create voice skills, turn Alexa into a Claude-powered assistant, integrate AWS services), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Good keyword coverage of natural terms users would say — "Amazon Alexa", "skills de voz", "assistente", "Smart Home", plus specific service names. Not a 5 because common variations like "Echo", "voice assistant", or "Alexa skill development" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Alexa voice skills with Claude as the LLM backend, the Auri project) makes it largely distinguishable. Not a 5 because the broad AWS service list (Lambda, DynamoDB, Lex) creates minor overlap risk with general AWS-development skills.

4 / 5

Total

15

/

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.

Validation — 15 / 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
sickn33/agentic-awesome-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.