CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. Trigger em: "integrar IA no app", "AI integration", "provider adapter de IA", "feature de IA", "chamar OpenAI", "chamar Anthropic", "Claude API", "LLM no app", "arquitetura de IA", "custo de IA", "fallback de provider", "rate limit de IA".

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 has a well-sequenced workflow with an excellent verification checkpoint, but it is dragged down by an over-detailed inline component catalog, dated session narrative in the Fontes section, and references to files that are not part of the skill bundle.

Suggestions

Move the Beautiful UI component catalog (20 components, 6 categories, licensing notes) out of SKILL.md into a reference file, keeping only a one-line pointer and the adoption caveat.

Trim the 'Fontes' section to the citation and its unconfirmed details; drop the session narrative about failed URL attempts and the WebFetch confirmation date, or relocate version/date-stamped details to a dedicated changelog section.

Either bundle the referenced pattern/policy files under the skill (e.g. references/) or state explicitly where they live, since none of the referenced paths (patterns/, policies/, docs/) exist inside this skill's directory.

DimensionReasoningScore

Conciseness

Core sections are lean, but the 'Camada Visual' section inlines a full catalog of 20 components across 6 categories plus licensing detail, and 'Fontes' includes session-narrative padding ('as tentativas anteriores na mesma sessao falharam por erro de digitacao') and time-stamped details (2026-08-23, v2.12.2+) outside any deprecated section — noticeably tighter than anchor 2 but with real trimmable content.

3 / 5

Actionability

Concrete, executable guidance is present: a required-reading list, a verification checkpoint ('rodar uma chamada real... forcar timeout ou erro 429'), and copy-paste bash for submodule init/update; the gap keeping it from 5 is that the actual adapter/hook design guidance lives entirely in external pattern files not present in this bundle.

4 / 5

Workflow Clarity

A clear sequence (Quando Usar -> Entradas -> Base Obrigatoria -> Checkpoint -> Evidencia -> Handoff) with an explicit validation feedback loop: 'Se o fallback nao disparar, corrigir o adapter e forcar o erro de novo antes de considerar a integracao pronta.' This matches the anchor with explicit validation steps and error recovery.

5 / 5

Progressive Disclosure

References (patterns/ai-integration/*.md, policies/*.md, templates/ai-integration-plan.md) are clearly signaled and one level deep, but none exist in this skill's bundle (no references/, scripts/, or assets/ directories), and the 20-component Beautiful UI catalog is inlined content that clearly belongs in a separate reference file.

3 / 5

Total

15

/

20

Passed

Description

96%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 strong description: concrete capabilities, an explicit 'Use quando' clause, and a rich bilingual trigger list. The only weakness is mild overlap risk with other AI-related skills on the broader trigger terms.

DimensionReasoningScore

Specificity

The description states concrete actions ('desenhar e implementar integracoes de IA') and comprehensively enumerates the architectural concerns it separates ('provider, adapter, hooks, observabilidade, custo e seguranca') plus three modalities (texto, imagem, video), matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

It explicitly answers both 'what' (design/implement AI integrations separating six named concerns) and 'when' ('Use quando o usuario quiser adicionar texto, imagem ou video ao app' plus a concrete trigger list), which is the anchor-5 pattern.

5 / 5

Trigger Term Quality

Twelve explicit natural trigger phrases in both Portuguese and English ('integrar IA no app', 'AI integration', 'chamar OpenAI', 'Claude API', 'LLM no app', 'fallback de provider', 'rate limit de IA') give comprehensive coverage including synonyms, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

AI-integration architecture is a distinct niche, but broad triggers like 'feature de IA', 'chamar OpenAI' and 'Claude API' carry minor overlap risk with adjacent AI skills (the body boundaries against Image Generator, the description does not); this sits between mostly-distinct and clear-niche, noticeably above the midpoint.

4 / 5

Total

19

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/25-ai-integration-architect/SKILL.md

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.