What is your-skill-name?

A starter template for creating a custom Anima skill for a device type. It explains where to define supported devices, allowed actions, safe no-ops, preference learning, reference knowledge, and action helpers.

Use it when building a new Anima device skill, defining device-specific decisions, exposing executable actions, or recording preferences learned from usage.

It gives developers a structure for turning a device adapter into a focused skill with clearly limited behavior. The template also highlights the parts that must be replaced before use.

your-skill-name — Skill by Fullive-AI

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/fullive-ai/anima/_template

Any agent

npx skills add Fullive-AI/Anima --skill _template

Clone the repo

git clone --depth 1 https://github.com/Fullive-AI/Anima

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 490 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00033	$0.00490
Opus 5	$0.00016	$0.00245
Sonnet 5	$0.00007	$0.00098
Haiku 4.5	$0.00003	$0.00049

Measured 3d ago against content hash 83c11f942e90, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

your-skill-name scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/actions.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/custom/_template/SKILL.md · 63 lines

What it actually says

Your Skill

This folder is a starter template for a user-authored Anima skill.

Before you use it:

Copy _template/ to skills/custom/<your-skill-name>/
Rename name: to a real skill name
Replace your_device_type with the device type your adapter emits
Update the references and scripts below

What This Skill Must Define

When the skill should be used
Which device types it supports
What actions it is allowed to emit
What counts as a safe no-op
How preferences should be learned over time

Load These Resources

references/knowledge.md for domain rules, comfort ranges, and device interactions.
references/decide.md when generating a single-device action.
references/learn.md when updating the learned profile from usage history.
scripts/actions.py for the runtime action helpers exposed to Anima.

Working Rules

Keep the description in frontmatter concrete so the skill is easy to trigger.
Only expose actions in scripts/actions.py that the target adapter can execute.
Prefer narrow, conservative decisions over broad generic prompts.

Fill-In Checklist

Frontmatter: Replace your-skill-name with a lowercase stable id such as fan or plant_watering.
metadata.device_types: Must match the device.type values your adapter produces.
references/knowledge.md: Add real target ranges, risk conditions, and interactions.
references/decide.md: Keep the output schema strict. Do not let the model invent actions.
references/learn.md: Keep the output structured. Avoid free-form essays.
scripts/actions.py: Only keep helpers that are valid for your device.

Common Mistakes

Using action names that no adapter actually supports
Forgetting to define when the correct decision is none
Writing vague descriptions like "smart control for devices"
Mixing multiple unrelated device types into one skill

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 63 lines · 33 tokens per session scan A 83c11f942e90

Subscribe to this mod's changes

your-skill-name is a skill published in the GitHub repository Fullive-AI/Anima (1,049 stars, last pushed 13d ago), licensed Apache-2.0. It adds 33 tokens to every session and 490 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens