ai-integration-architect

Skill para desenhar e implementar integracoes de IA em aplicacoes, separando provider, adapter, hooks, observabilidade, custo e seguranca. Use quando o usuario quiser adicionar texto, imagem ou video ao app.

Quality

54%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/25-ai-integration-architect/SKILL.md

Quality

Discovery

67%

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 has a solid structure with explicit 'Use when' guidance, which is good for completeness. However, it relies on architectural jargon (provider, adapter, hooks) rather than concrete user-facing actions, and the trigger terms are too broad ('texto, imagem ou video') which could cause conflicts with other media-related skills.

Suggestions

Add more specific concrete actions like 'implement streaming AI responses', 'configure API rate limiting', 'set up prompt templates', or 'integrate with OpenAI/Anthropic APIs'.

Include natural trigger terms users would actually say: 'LLM integration', 'AI API', 'OpenAI', 'Claude API', 'chatbot', 'embeddings', 'prompt engineering'.

Make the 'Use when' clause more distinctive by specifying AI-specific scenarios rather than generic 'texto, imagem ou video' which could match many non-AI skills.

Dimension	Reasoning	Score
Specificity	Names the domain (AI integrations) and lists architectural components (provider, adapter, hooks, observability, cost, security), but doesn't describe concrete actions like 'implement streaming responses' or 'configure rate limiting'.	2 / 3
Completeness	Explicitly answers both what (design and implement AI integrations with separation of concerns) and when ('Use quando o usuario quiser adicionar texto, imagem ou video ao app'), providing clear trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'texto, imagem ou video' and 'integracoes de IA', but misses common natural language triggers users would say like 'LLM', 'API', 'OpenAI', 'Claude API', 'AI chat', 'embeddings', or 'prompt'.	2 / 3
Distinctiveness Conflict Risk	The focus on AI integrations with architectural separation is somewhat specific, but 'adicionar texto, imagem ou video' is quite broad and could overlap with general media handling, content management, or UI component skills.	2 / 3
	Total	9 / 12 Passed

Implementation

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill functions more as a routing document than an actionable guide. While it has good progressive disclosure with clear references to external patterns and policies, it lacks concrete implementation guidance, executable examples, or specific architectural decisions. The skill tells Claude what to consult but not how to actually implement AI integrations.

Suggestions

Add at least one concrete code example showing a minimal adapter or hook implementation pattern

Include a specific workflow with numbered steps and validation checkpoints (e.g., '1. Read provider requirements -> 2. Validate cost constraints -> 3. Implement adapter')

Provide a concrete example of expected output format (e.g., sample architecture decision document or adapter interface)

Remove or consolidate the governance references into a single line to reduce overhead

Dimension	Reasoning	Score
Conciseness	The skill is reasonably concise but includes some redundant sections (e.g., 'Quando Usar' vs 'Quando Nao Usar' could be tighter). The governance references add overhead without immediate value in the body.	2 / 3
Actionability	No concrete code, commands, or executable examples. The skill describes what to consult and what outputs to produce but provides no actual implementation guidance, patterns, or copy-paste ready content.	1 / 3
Workflow Clarity	There's an implicit workflow (consult patterns -> decide architecture -> handoff), but no explicit sequencing, validation checkpoints, or feedback loops for error recovery. Steps are listed but not actionable.	2 / 3
Progressive Disclosure	Good structure with clear references to external files (patterns/, policies/, templates/). References are one level deep and well-signaled with specific file paths for different concerns.	3 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: felvieira/claude-skills-fv
Commit: 524725e

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.