CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-transfer

Transfer reusable prevention lessons from another AI Factory project into the current project's skill-context through /aif-evolve. Use when building a similar project and you want to avoid problems already captured in another project's patches without copying or revealing that project's identity, paths, or identifiers.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 delivers an exemplary gated workflow: precisely sequenced steps, exact paths and defaults, and privacy validation loops both before and after writes. Its weaknesses are token efficiency — generic tool-interaction policy inlined up front and privacy rules repeated in four places — and missed opportunity to split boilerplate into reference files since no bundle structure exists.

Suggestions

Move the "Runtime-aware questions" and "Shared project skill-context" boilerplate sections into a reference file (e.g. references/interaction-policy.md) and keep a one-line pointer, removing ~30 lines of generic policy from the body and improving progressive_disclosure.

State the privacy rules once in the Non-Negotiable Privacy Contract and reduce Steps 4, 5, and 7 to short checklists that reference it, cutting repeated prose to improve conciseness.

Add a brief "Outputs" section near the top summarizing which files may be written and only after approval, so the write targets do not have to be inferred from Steps 5-7.

DimensionReasoningScore

Conciseness

The workflow steps themselves are dense and skill-specific, but the opening "Runtime-aware questions" section spends ~15 lines on generic question-tool interaction policy Claude already knows, and the privacy requirements are restated across the Non-Negotiable Privacy Contract, Steps 4, 5, and 7, and the final Rules list. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not severely padded enough for a 2.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact file paths (".ai-factory/skill-context/aif-transfer/SKILL.md"), concrete config keys and defaults ("description: .ai-factory/DESCRIPTION.md", "ui_language: en"), a deterministic ID scheme ("experience-001"), usage examples with quoted paths, an exhaustive source-read allowlist, and explicit accept/reject criteria for every gate. Per the rubric's code-vs-instruction note, absence of code is not penalized when guidance is this concrete.

5 / 5

Workflow Clarity

Steps 0-7 are clearly sequenced with validation at every stage: argument validation and source-sanity checks in Step 0, the relevance gate in Step 3, privacy preflight in Step 5, and post-write re-verification in Step 7. Explicit feedback loops are present ("On any match, rewrite or remove the affected candidate and repeat the full preflight"; "If a leak is found, remove or rewrite it immediately and re-check all changed files"), satisfying the batch/write-operation feedback-loop requirement.

5 / 5

Progressive Disclosure

The single file is well-sectioned with clear headers, and its one external pointer ("{{skills_dir}}/aif-evolve/SKILL.md") is clearly signaled and one level deep. However, no bundle files exist and ~30 lines of generic interaction and skill-context boilerplate ("Runtime-aware questions", "Shared project skill-context") are inlined in a ~290-line file when they could live in a shared reference, matching 'some structure but content that should be separate is inline'.

3 / 5

Total

16

/

20

Passed

Description

82%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 with an explicit what-and-when structure, natural trigger phrasing, and a well-delineated niche that minimizes conflict with other skills. The only real deduction is the second-person voice ("you want to avoid") and action coverage that names the core transfer action rather than enumerating several distinct capabilities.

DimensionReasoningScore

Specificity

The description names the domain and a concrete action chain ("Transfer reusable prevention lessons ... into the current project's skill-context through /aif-evolve") plus privacy constraints, which sits between the 3 and 4 anchors (1-2 concrete actions vs. several). However, the second-person phrasing "you want to avoid problems" incurs the rubric's 1-point specificity penalty, lowering the base of 4 to 3.

3 / 5

Completeness

It explicitly answers both questions: what ("Transfer reusable prevention lessons ... through /aif-evolve") and when ("Use when building a similar project and you want to avoid problems already captured in another project's patches"), with concrete trigger conditions. Anti-drift check against the 4 anchor confirms the 'when' clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("building a similar project", "avoid problems", "another project's patches"), matching the good-coverage anchor, but common synonyms users might say such as "reuse lessons" or "apply learnings from another project" are missing, so it is not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche anchored in AI Factory-specific machinery ("/aif-evolve", "skill-context", "another AI Factory project"), so it is unlikely to trigger for unrelated skills and carries minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-transfer/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.