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

83%

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 core is a well-staged architecture workflow with an exemplary validate-and-retry checkpoint and copy-paste submodule commands, but it is diluted by two sections of inlined research notes about a UI component library (catalog details, license, live-verification dates, a URL-typo anecdote) that add noise and time-sensitive claims. Referenced detail files are clearly signaled but absent from the bundle, and the UI-library material should live in a separate reference rather than the overview.

Suggestions

Move the Beautiful UI material — the 20-component/6-category catalog, license and stack caveats, and adoption conditions — out of SKILL.md into a one-level-deep reference file (e.g. references/ui-components.md), keeping a single pointer line in the handoff section.

Strip the research-process narration from "Fontes" and the visual-layer section: the WebFetch confirmation date, the URL-typo anecdote, and "v2.12.2" version pinning either belong in a maintenance/deprecated section or should be removed in favor of stable statements.

Since none of the referenced files (patterns/, policies/, templates/, docs/, sources/) ship in this bundle, either include them or note explicitly that the skill requires the parent kit repo, so the dangling references do not read as broken navigation.

DimensionReasoningScore

Conciseness

Core sections (Quando Usar, Entradas, Saidas, Base Obrigatoria, Checkpoint, Handoff) are tight lists, but the "Camada Visual" and "Fontes" sections pad roughly a third of the body with a 20-component/6-category catalog, license details, verification dates ("confirmado ao vivo em 2026-08-23", "v2.12.2+"), and a URL-typo anecdote ("as tentativas anteriores na mesma sessao falharam por erro de digitacao"). Not a 2 because the architectural core assumes Claude's competence with no concept explanations; not a 4 because the research-log digression is substantial and the time-sensitive date/version details further penalize per the guidelines.

3 / 5

Actionability

Concrete and executable where it counts: a specific required-reading file list, a real-call checkpoint with forced failure conditions ("forçar timeout ou erro 429 e ver o adapter reagir como desenhado"), and copy-paste git submodule commands. Not a 5 because the central architecture deliverable itself is never shown or templated (the plan template is only referenced by path), leaving minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

The workflow is explicitly staged — inputs, "Antes de decidir a arquitetura, consultar" the base files, "Checkpoint antes de fechar a arquitetura" with a real validation call, "Evidencia de Conclusao", then handoff — and includes a genuine feedback loop: "Se o fallback não disparar, corrigir o adapter e forçar o erro de novo antes de considerar a integração pronta" (validate → fix → retry). This matches the top anchor's explicit validation with error recovery; not a 4 because the checkpoint and retry loop are fully specified, not merely present.

5 / 5

Progressive Disclosure

References to pattern/policy/template files are clearly signaled and one level deep, but none of the referenced paths (patterns/ai-integration/*.md, policies/*.md, templates/ai-integration-plan.md, docs/patterns/submodule-skills.md, the anthropic-cookbook submodule) exist in the provided bundle, so none can be verified or navigated. Additionally, the Beautiful UI component catalog and its sourcing/verification notes are inlined detail that belongs in a separate reference file. Not a 2 because the SKILL.md itself is well sectioned and the reference structure (not the inlining) is the intended design of a larger kit; not a 4 because unresolvable references plus a substantial inline block that should be separate are more than minor organization gaps.

3 / 5

Total

15

/

20

Passed

Description

91%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 that explicitly states what the skill does, the concerns it separates, and an explicit trigger list of twelve natural user phrases in two languages, all in third person. The only weaknesses are actions stated at a fairly abstract design level and trigger terms like "chamar OpenAI"/"Claude API" that overlap slightly with provider-API reference skills.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("desenhar e implementar integracoes de IA em aplicacoes") and enumerates the architectural concerns it separates ("provider, adapter, hooks, observabilidade, custo e seguranca"). Not a 5 because the actions stay at the design/implement level rather than naming concrete deliverables or operations, leaving minor coverage gaps.

4 / 5

Completeness

Clearly answers both what ("desenhar e implementar integracoes de IA em aplicacoes, separando provider, adapter, hooks, observabilidade, custo e seguranca") and when (explicit "Trigger em:" clause with concrete trigger phrases), matching the top anchor exactly; not below because neither half is vague or implicit.

5 / 5

Trigger Term Quality

Twelve natural trigger phrases in both Portuguese and English ("integrar IA no app", "AI integration", "chamar OpenAI", "chamar Anthropic", "Claude API", "LLM no app", "arquitetura de IA", "custo de IA", "fallback de provider", "rate limit de IA") — comprehensive coverage including provider names, synonyms, and common user phrasings.

5 / 5

Distinctiveness Conflict Risk

The niche (integration architecture with fallback/rate-limit/cost concerns) is mostly distinct, but triggers like "chamar OpenAI", "chamar Anthropic" and "Claude API" could fire for simple provider-API questions handled by closely related skills. Not a 5 due to that minor overlap risk; not a 3 because the architectural trigger terms ("arquitetura de IA", "fallback de provider") are clearly niche-specific.

4 / 5

Total

18

/

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.