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

86%

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

Quality

Content

72%Weight 40%Scale 1-3

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

A lean, well-structured skill body that avoids concept re-explanation and organizes references one level deep. Its main weakness is that core guidance points to external pattern files without concrete in-skill examples or an explicit validated workflow sequence.

Suggestions

Add a minimal concrete example of an adapter/hook signature inline so the skill is actionable without first opening the pattern files.

Replace the implicit consult-design-handoff flow with an explicit numbered sequence, including a validation checkpoint before handoff.

Trim the submodule section to the essential init/update commands and drop the version-pinning and inspiration-link detail to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient bullet structure with no concept re-explanation, but the 'Docs upstream via submodule' section pads two bash blocks, version pinning, and an inspiration link that don't all earn their place — the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Guidance is concrete in structure (expected inputs/outputs, a 'Base Obrigatoria' file list, executable submodule commands) but the core task guidance is 'consultar' pointers to pattern files rather than executable adapter/hook examples, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	Sections imply a flow (consult base files -> design -> handoff) and 'Evidencia de Conclusao' acts as a checklist, but there is no explicit sequenced multi-step workflow with validation checkpoints, matching 'steps listed but validation gaps / checkpoints implicit'.	2 / 3
Progressive Disclosure	Well-organized overview sections with clearly signaled, one-level-deep references ('Base Obrigatoria' listing patterns/ai-integration/*.md, 'Handoff' to policies/handoffs.md); no nested reference chains and easy navigation, fitting the clear-overview anchor.	3 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person description that clearly states capabilities, provides explicit 'Use when' guidance, and lists natural trigger terms. It answers both what the skill does and when to invoke it with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain plus concrete actions/aspects — 'desenhar e implementar integracoes de IA' while 'separando provider, adapter, hooks, observabilidade, custo e seguranca' enumerates multiple specific responsibilities, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('desenhar e implementar integracoes de IA...') and when ('Use quando o usuario quiser adicionar texto, imagem ou video ao app' plus an explicit Trigger list), satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	The 'Trigger em' list covers natural phrases a user would say — 'integrar IA no app', 'chamar OpenAI', 'chamar Anthropic', 'Claude API', 'LLM no app', 'fallback de provider', 'rate limit de IA' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The architecture/provider-adapter/hooks framing carves a clear niche ('arquitetura de IA', 'provider adapter de IA', 'fallback de provider') unlikely to fire for unrelated skills, matching the distinct-triggers anchor.	3 / 3
	Total	12 / 12 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: 030ef22

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