Agent skill

Anima Upgrade Migration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Analyze and execute @animaapp/anima-sdk upgrades with rollback evidence.

MITAuto-check passedDevelopment

Install Anima Upgrade Migration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-upgrade-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace anima-upgrade-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/anima-upgrade-migration .claude/skills/anima-upgrade-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
anima-upgrade-migration
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
486 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Analyze and execute @animaapp/anima-sdk upgrades with rollback evidence.

  • Works in 3 steps: Upgrade SDK → Migrate from Manual Plugin to SDK → API Changes Checklist
  • Upgrading SDK versions
  • SKILL.md covers Overview, Prerequisites, Migration Paths and Instructions, plus 5 more sections
  • Calls npm; needs ANIMA_TOKEN and FIGMA_FILE_KEY

What it does

Anima Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze and execute @animaapp/anima-sdk upgrades with rollback evidence. Use when upgrading SDK versions, migrating from the Figma plugin workflow to SDK-based automation, or adapting to new Anima API features. Trigger with: "anima upgrade", "anima migration", "anima SDK update".

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access

It sits in Development. It works with Figma. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Upgrading SDK versions
  • Migrating from the Figma plugin workflow to SDK-based automation
  • Adapting to new Anima API features
  • With: anima upgrade

Example prompts

  • “anima upgrade”
  • “anima migration”
  • “anima SDK update”
  • “/anima-upgrade-migration”

Requirements

  • Node.js
  • A credential in ANIMA_TOKEN
  • A credential in FIGMA_FILE_KEY
  • Compatibility (from SKILL.md): Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Grep

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Upgrade SDK
  2. Migrate from Manual Plugin to SDK
  3. API Changes Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(npm:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • npmjs.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • ANIMA_TOKEN
    • FIGMA_FILE_KEY
    • FIGMA_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access

    From compatibility in the SKILL.md frontmatter.

Context cost

Anima Upgrade Migration loads about 1.8k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 486 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 486 words, ~1,771 tokens.

Download SKILL.mdSave it as .claude/skills/anima-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
anima-upgrade-migration
description
Analyze and execute @animaapp/anima-sdk upgrades with rollback evidence. Use when upgrading SDK versions, migrating from the Figma plugin workflow to SDK-based automation, or adapting to new Anima API features. Trigger with: "anima upgrade", "anima migration", "anima SDK update".
allowed-tools
Read, Write, Edit, Bash(npm:*), Grep
compatibility
Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access
version
2.0.0
argument-hint
[target-sdk-version]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, design, figma, anima, migration

Anima Upgrade & Migration

Overview

This workflow moves an Anima integration between SDK versions or from manual Figma exports to automation while preserving a reviewable, reversible design source of truth. It uses a pinned dependency and a staging canary so API or generated-code changes are detected before production output is replaced.

Prerequisites

  • A clean working tree, committed lockfile, current SDK version, and a reviewed changelog or release note for the proposed target version.
  • A fixture registry containing synthetic or approved design nodes, expected output paths, and a baseline artifact digest for the current workflow.
  • Separate staging credentials with read-only design access, an owner for generated-code review, and a rollback revision that can restore the prior SDK and generated output.
  • CI gates for install, lint, type checking, tests, and secret scanning; do not test an upgrade against customer designs or live production writes.

Migration Paths

FromToComplexity
Figma plugin (manual)SDK automationMedium
Older pinned SDKExplicit reviewed targetDepends on release/type/generated-output diff
Anima PlaygroundSDK APILow

Instructions

Step 1: Upgrade SDK
bash
# Check current version
npm list @animaapp/anima-sdk

# Select and record a concrete target; 0.27.0 was current on 2026-09-12.
export APPROVED_ANIMA_VERSION="0.27.0"
npm install --save-exact "@animaapp/anima-sdk@${APPROVED_ANIMA_VERSION}"

# Check for breaking changes
npm view "@animaapp/anima-sdk@${APPROVED_ANIMA_VERSION}" version dist.integrity
Step 2: Migrate from Manual Plugin to SDK
typescript
// BEFORE: Manual Figma plugin workflow
// 1. Open Figma → Plugins → Anima
// 2. Select component → Export → React
// 3. Copy-paste generated code into project
// 4. Manually repeat for each component change

// AFTER: Automated SDK workflow
import { Anima } from '@animaapp/anima-sdk';
import fs from 'node:fs';
import path from 'node:path';

const anima = new Anima({ auth: { token: process.env.ANIMA_TOKEN! } });

// Automated: runs in CI on Figma file version change
async function syncDesignToCode() {
  const { files } = await anima.generateCode({
    fileKey: process.env.FIGMA_FILE_KEY!,
    figmaToken: process.env.FIGMA_TOKEN!,
    nodesId: ['1:2', '3:4', '5:6'],  // All design system components
    settings: { language: 'typescript', framework: 'react', styling: 'tailwind' },
  });

  // Write to project, run through linter, create PR
  const root = path.resolve('src/components/generated');
  for (const [fileName, file] of Object.entries(files)) {
    if (file.isBinary) throw new Error(`Review binary output separately: ${fileName}`);
    const target = path.resolve(root, fileName);
    if (!target.startsWith(`${root}${path.sep}`)) throw new Error('Unsafe output path');
    fs.mkdirSync(path.dirname(target), { recursive: true });
    fs.writeFileSync(target, file.content);
  }
}
Step 3: API Changes Checklist
typescript
// Common API changes between versions:
// - New settings options (e.g., uiLibrary: 'shadcn' added later)
// - Supported framework, styling, and UI-library unions
// - Response record shape and binary-file handling
// - Authentication, Figma access, streaming, and error types

// Test after upgrade:
async function testUpgrade() {
  const anima = new Anima({ auth: { token: process.env.ANIMA_TOKEN! } });
  const { files } = await anima.generateCode({
    fileKey: process.env.FIGMA_FILE_KEY!,
    figmaToken: process.env.FIGMA_TOKEN!,
    nodesId: ['1:2'],
    settings: { language: 'typescript', framework: 'react', styling: 'tailwind' },
  });
  console.log(`Upgrade test: ${Object.keys(files).length} files generated`);
}

Error Handling

FailureRequired response
Dependency resolution or lockfile changes are unexpectedStop the migration, inspect the dependency tree, and restore the approved lockfile before retrying.
Authentication, file access, or API schema changes failKeep the old revision active; verify credentials and supported request fields without widening access.
Generated files move, disappear, or contain an unexpected diffQuarantine the output, compare against the baseline fixture, and require owner review before any merge.
Lint, type, visual, or accessibility checks failDo not promote the SDK; retain the sanitized test receipt and return the failure to the design/code owner.
Staging canary fails or rollback is unavailableDisable automated generation and restore the last known-good package and generated artifact.

Never log tokens, full Figma payloads, or design content while comparing versions. A migration is complete only after the pinned package, source version, artifact digest, test result, and rollback reference are recorded.

Show full SKILL.md (153 more words)Show less

Tool Discipline

Use Read and Grep to inspect the existing integration and generated diff before changing anything. Use Write or Edit only inside the approved generated-code, test, or configuration paths. Use the declared Bash commands only for the explicit install, validation, or diagnostic steps in this workflow; never print tokens, source designs, generated source, or private website captures.

Output

  • SDK upgraded to the explicitly approved pinned version
  • Migrated from manual plugin to automated SDK
  • All generation tests passing after upgrade

Examples

Use an approved version and one synthetic, allowlisted component for a staged canary; keep the lockfile and generated diff in the review boundary:

bash
export APPROVED_ANIMA_VERSION="2.x.y"
npm install "@animaapp/anima-sdk@${APPROVED_ANIMA_VERSION}"
npm test
npm run lint
npm run generate:staging -- \
  --file-key synthetic-staging-file \
  --node-id 1:2 \
  --output-dir .tmp/anima-upgrade \
  --no-production-write

Compare the staged artifact with the baseline, review the source-version and path changes, and promote only after owner approval. If the canary changes an unexpected file or fails a quality gate, delete the temporary output and restore the prior lockfile/package before rerunning.

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/anima-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Anima Upgrade Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Anima Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Anima Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: PassMIT
Figma Typings Auditawdr74100/figwright1k—~3.3kAutomated safety check: PassMIT
Prepare Releaseneetly/figma-agent-linux396—~833Automated safety check: PassMIT
Prototype First UIDejavuMoe/Smoji115—~4.2kAutomated safety check: PassApache-2.0
Spec App Consistency Auditleo-kuang-ai/spec-first107—~4.6kAutomated safety check: PassMIT
Dyl Modecursor/plugins11k—~1.7kAutomated safety check: PassNone

Similar skills

  • Figma Typings Audit

    awdr74100/figwright

    Upgrade @figma/plugin-typings and absorb what the new version exposes.

    1k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Prepare Release

    neetly/figma-agent-linux

    Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes.

    396 GitHub stars~833 tokensUpdated today
    DevelopmentAuto-check passed
  • Prototype First UI

    DejavuMoe/Smoji

    Run a safe prototype-first UI/UX workflow across web, desktop, mobile, extensions, and multimodal design inputs.

    115 GitHub stars~4.2k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Spec App Consistency Audit

    leo-kuang-ai/spec-first

    Audit mobile App PRD/Figma/local-source consistency across page routes, KMP/Clean Architecture, components, analytics, i18n, engineering quality, and industry lenses before runtime validation; use…

    107 GitHub stars~4.6k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Dyl Mode

    cursor/plugins

    Official

    Dylan's agent style on top of pstack: concise verified delivery, root causes over symptom patches, The Algorithm before design, plain /bro replies, live UI proof, reuse/simplify, and hard merge gates.

    11k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Building Web PRs

    Comfy-Org/ComfyUI_frontend

    Builds a comfy.org website change from a design-team request and takes it to a reviewed pull request, or to a hand-off naming what is still open and who must act.

    2.1k GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Questions about Anima Upgrade Migration

What does Anima Upgrade Migration do?

Analyze and execute @animaapp/anima-sdk upgrades with rollback evidence. Anima Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze and execute @animaapp/anima-sdk upgrades with rollback evidence.

When should I use Anima Upgrade Migration?

Anima Upgrade Migration fits situations like: upgrading SDK versions; migrating from the Figma plugin workflow to SDK-based automation; adapting to new Anima API features; with: anima upgrade.

How do I install Anima Upgrade Migration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/anima-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/anima-upgrade-migration in your project. Claude Code loads it when a task matches its description.

How do I install Anima Upgrade Migration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/anima-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/anima-upgrade-migration in your project. Codex loads it when a task matches its description.

Can I use Anima Upgrade Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-upgrade-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/anima-upgrade-migration, .gemini/skills/anima-upgrade-migration, .github/skills/anima-upgrade-migration and .opencode/skills/anima-upgrade-migration in your project.

What does Anima Upgrade Migration need to run?

Going by SKILL.md and its folder, Anima Upgrade Migration needs the command-line tools its instructions call (npm) and credentials named ANIMA_TOKEN, FIGMA_FILE_KEY and FIGMA_TOKEN. Our summary lists: Node.js; A credential in ANIMA_TOKEN; A credential in FIGMA_FILE_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*), Grep. Compatibility (from SKILL.md): Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access.

Does Anima Upgrade Migration access the network?

SKILL.md names 2 domains. As links in the text: npmjs.com and github.com. This is read from the text; nothing was executed.

Is Anima Upgrade Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Anima Upgrade Migration use?

Anima Upgrade Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Anima Upgrade Migration use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 198 tokens, read only when the agent opens those files.

What are the alternatives to Anima Upgrade Migration?

Skills that share tags, products or a category with Anima Upgrade Migration: Figma Typings Audit (awdr74100/figwright, 1k stars), Prepare Release (neetly/figma-agent-linux, 396 stars), Prototype First UI (DejavuMoe/Smoji, 115 stars) and Spec App Consistency Audit (leo-kuang-ai/spec-first, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Anima Upgrade Migration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.