agentleFS
hyf020908hyf020908/modelscope-skills/skills/transformers.js/SKILL.md

transformers-js

Skill4 starsChanged 8 months agoApache-2.0View on GitHub

Build browser or Node.js inference workflows from plain-language requests using Transformers.js and locally downloaded model assets.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use huggingface-paper-publisher, huggingface-spaces and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hugging FaceSkill

    huggingface-paper-publisher

    Publish and manage research papers on Hugging Face Hub. Supports creating paper pages, linking papers to models/datasets, claiming authorship, and generating professional markdown-based research articles.

    Also in 3 projects that use this

  • Hugging FaceSkill

    huggingface-spaces

    Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't build or run, or otherwise work with `hf spaces …`, `@spaces.GPU`, Space README frontmatter, or the `spaces` Python package.

    Also in 3 projects that use this

  • +6 more from huggingface

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants JS or TS inference and describes the behavior in natural language.

    line 8
  2. Distinctive:

    Leave the project runnable with clear install and run commands.

    line 21
  3. Distinctive:

    Keep local model paths explicit.

    line 25
  4. Distinctive:

    Prefer the smallest runnable example over framework-heavy scaffolding.

    line 26
  5. Distinctive:

    Never hide where model artifacts come from.

    line 41
  6. Very specific:

    Never assume browser-only code will run in Node.js or the reverse.

    line 42
  7. Distinctive:

    Keep asset caching deterministic.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Transformers.js For ModelScope Workflows

Use this skill when the user wants JS or TS inference and describes the behavior in natural language.

Request Style

  • Accept requests such as:
    • Make a small Node.js text-classification demo.
    • 做一个浏览器端摘要页面,模型文件先下载到本地。

Workflow

  1. Decide whether the runtime is browser, Node.js, or both.
  2. Download model assets explicitly to a local folder.
  3. Load them with @huggingface/transformers.
  4. Leave the project runnable with clear install and run commands.

Rules

  • Keep local model paths explicit.
  • Prefer the smallest runnable example over framework-heavy scaffolding.
  • Pin versions when editing production code.

References

  • references/EXAMPLES.md
  • references/TEXT_GENERATION.md
  • references/PIPELINE_OPTIONS.md
  • references/CONFIGURATION.md
  • references/CACHE.md

Load only what the current task needs.

Guardrails

  • Never hide where model artifacts come from.
  • Never assume browser-only code will run in Node.js or the reverse.
  • Keep asset caching deterministic.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.