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".

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/25-ai-integration-architect/SKILL.md

Quality

Content

60%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 well-structured architecture-routing skill with clear sections, named references, and a completion checklist, but it leans on reference pointers over concrete decision guidance and carries verbose reconnaissance trivia in the Beautiful UI and submodule sections.

Suggestions

Move the Beautiful UI component catalog and the submodule setup details into separate reference files, keeping SKILL.md to a one-paragraph pointer plus the key caveat.

Replace the 'consultar <files>' guidance for the core decision with a short concrete decision sequence (e.g., 1. read use case + stack, 2. match provider/gateway from providers.md, 3. choose hooks from hooks.md, 4. record choice + justification in the plan).

Trim reconnaissance trivia (live-confirmation dates, URL-typo anecdote, repeated confirmation story in Fontes) since it does not aid execution.

Dimension	Reasoning	Score
Conciseness	Core sections (Quando Usar, Entradas, Saidas, Base Obrigatoria) are lean, but the 'Camada Visual' and 'Docs upstream via submodule' sections pad in reconnaissance trivia (full component catalog, live-confirmation dates, a URL-typo anecdote) Claude does not need.	3 / 5
Actionability	Gives concrete pointers (consult named pattern files, follow named policies, named handoff targets, copy-pasteable submodule commands), but the central architecture decision is mostly described via 'consultar' references rather than concrete decision steps.	3.5 / 5
Workflow Clarity	A rough sequence is implied (Entradas -> Base Obrigatoria -> decidir -> Evidencia de Conclusao -> Handoff) and a completion checklist exists, but steps are unnumbered with no explicit validation/feedback checkpoints.	3.5 / 5
Progressive Disclosure	Clear sections with one-level-deep pattern-file references and signaled handoff pointers; minor gaps because two long sections (Beautiful UI catalog, submodule setup) are inlined rather than split into separate reference files, and no bundle files exist alongside.	4 / 5
	Total	14 / 20 Passed

Description

95%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, specific description with explicit what/when guidance and a rich set of natural trigger phrases including provider names and synonyms. The main weakness is slightly high-level action verbs and a couple of broad triggers that risk minor overlap.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (desenhar e implementar integracoes, separar provider/adapter/hooks/observabilidade/custo/seguranca) and three media types, but the actions stay somewhat high-level rather than enumerating many distinct operations as in the 5-anchor.	4.5 / 5
Completeness	Clearly states what the skill does and gives an explicit 'Use quando...' clause plus a 'Trigger em:' list of concrete trigger phrases, matching the 5-anchor.	5 / 5
Trigger Term Quality	Comprehensive explicit trigger list with synonyms (IA/AI/LLM), provider names (OpenAI, Anthropic, Claude API) and concrete concerns (custo, fallback, rate limit) that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (IA integration architecture with provider/adapter/hooks separation) and specific provider-name triggers, but broad terms like 'feature de IA'/'LLM no app' carry minor overlap risk with general coding skills.	4.5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: f3492ef

Reviewed: 5 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.