BC face-swap-runcomfy
Face swap on RunComfy. This RunComfy face swap skill substitutes a face or character into video or still images via the `runcomfy` CLI. Routes across community Wan 2-2 Animate (RunComfy's character-swap feature pick — audio-driven full-body identity swap into video), Kling 2-6 Motion Control Pro (transfer source-video motion onto a target character), Nano Banana 2 Edit (1–20 batch identity-preserving still face swap), GPT Image 2 Edit (multi-ref compositional still face swap with explicit role assignment), and FLUX Kontext Pro (single-ref precise local face edit). The RunComfy face swap skill picks the right model for intent — still vs video, single-shot vs batch, photoreal vs stylized, motion-preserving vs identity-preserving. Triggers on "face swap", "swap face", "deepfake", "face replacement", "character swap", "head swap", "put X's face on Y", "make this video star X", "replace the actor in this video", "swap the character in the photo", "deepfake video", "ReActor alternative", or any explicit ask to substitute one identity for another with RunComfy.
Face swap on RunComfy.
As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1071 chars, limit 1024 - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "clawdis"
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4174 tokens
- 85Steps. 42 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1070: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +4Structure: 34 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.