Agent skill

Provider Adapter Development

by AbdelStark in AbdelStark/worldforge

A skill your agent uses for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching…

MITAuto-check: notesDevelopment

Install Provider Adapter Development

skills CLI
$ npx skills add AbdelStark/worldforge --skill provider-adapter-development -a claude-code

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

GitHub CLI
$ gh skill install AbdelStark/worldforge provider-adapter-development --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/AbdelStark/worldforge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/provider-adapter-development .claude/skills/provider-adapter-development && 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
provider-adapter-development
GitHub stars
108
Token cost
~990 tokens
SKILL.md length
400 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching…

  • Works in 9 steps: Read the closest existing adapter, then… → Classify the upstream runtime by what it… → For a new scaffold, start with uv run… → …
  • WorldForge provider work: adding adapters
  • SKILL.md covers Non-Negotiables, Capability Map, Workflow and Definition Of Done, plus 1 more section
  • Calls uv

What it does

Provider Adapter Development is an agent skill from AbdelStark/worldforge. Use for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching LeWorldModel, GR00T, LeRobot, Cosmos-Policy, JEPA, Genie, or JEPA-WMS. Ensures capabilities remain truthful and optional runtimes stay host-owned.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Project scaffolding. The repository describes itself as: Harness framework to build world model based workflows for physical AI systems. The licence is MIT.

When your agent uses it

  • WorldForge provider work: adding adapters
  • Changing capability declarations
  • Promoting scaffolds
  • Debugging provider failures

Example prompts

  • “/provider-adapter-development”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Read the closest existing adapter, then src/worldforge/providers/base.py, src/worldforge/providers/catalog.py, and…
  2. Classify the upstream runtime by what it actually does, not by model marketing language.
  3. For a new scaffold, start with uv run python scripts/scaffold_provider.py ...; keep capabilities unadvertised until real methods return…
  4. Validate public inputs before network calls, filesystem reads, or optional runtime calls.
  5. Return the correct public model: PredictionPayload, EmbeddingResult, ActionScoreResult, or ActionPolicyResult.
  6. Add success and malformed/error fixtures under tests/fixtures/providers/.
  7. Add worldforge.testing.assert_provider_contract() coverage for every advertised capability.
  8. Update .env.example, provider docs, generated catalog surfaces, README, changelog, AGENTS.md, or CLAUDE.md only when public behavior or…
  9. Validate with focused provider tests, ruff, generated provider-doc check, and the coverage/package gates when the public surface changes.

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

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

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Provider Adapter Development loads about 990 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 400 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~990

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:55
    e name from `.env.example`; do not read `.env` |

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 AbdelStark/worldforge at commit 30b65da, republished under its MIT licence (© AbdelStark). 400 words, ~990 tokens.

Download SKILL.mdSave it as .claude/skills/provider-adapter-development/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
provider-adapter-development
description
Use for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching LeWorldModel, GR00T, LeRobot, Cosmos-Policy, JEPA, Genie, or JEPA-WMS. Ensures capabilities remain truthful and optional runtimes stay host-owned.

Provider Adapter Development

Non-Negotiables

  • Valid capabilities are predict, embed, plan, score, and policy.
  • ProviderCapabilities() is fail-closed. Advertise only callable, tested operations.
  • plan is a WorldForge facade workflow. Do not benchmark or advertise it as a provider operation unless a real provider-owned planner exists.
  • Optional runtimes, checkpoints, datasets, CUDA, robot packages, credentials, and robot controllers stay out of base dependencies and repo artifacts.
  • Provider events are a log boundary. Never emit bearer tokens, API keys, signed URL query strings, or secret-like metadata.
  • Treat upstream marketing names as untrusted. Capability labels come from observed callable behavior and contract tests, not from model family branding.

Capability Map

ProviderTruthful surfaceRegistration
mockpredict, embedalways
cosmos-policypolicyCOSMOS_POLICY_BASE_URL
leworldmodelscoreLEWORLDMODEL_POLICY or LEWM_POLICY
gr00tpolicyGROOT_POLICY_HOST
lerobotpolicyLEROBOT_POLICY_PATH or LEROBOT_POLICY
jepascoreJEPA_MODEL_NAME
geniescaffold onlyenv-gated reservation
jepa-wmsdirect-construction score candidatenot exported or auto-registered

Workflow

  1. Read the closest existing adapter, then src/worldforge/providers/base.py, src/worldforge/providers/catalog.py, and docs/src/provider-authoring-guide.md.
  2. Classify the upstream runtime by what it actually does, not by model marketing language.
  3. For a new scaffold, start with uv run python scripts/scaffold_provider.py ...; keep capabilities unadvertised until real methods return validated WorldForge models.
  4. Validate public inputs before network calls, filesystem reads, or optional runtime calls.
  5. Return the correct public model: PredictionPayload, EmbeddingResult, ActionScoreResult, or ActionPolicyResult.
  6. Add success and malformed/error fixtures under tests/fixtures/providers/.
  7. Add worldforge.testing.assert_provider_contract() coverage for every advertised capability.
  8. Update .env.example, provider docs, generated catalog surfaces, README, changelog, AGENTS.md, or CLAUDE.md only when public behavior or env vars change.
  9. Validate with focused provider tests, ruff, generated provider-doc check, and the coverage/package gates when the public surface changes.
Show full SKILL.md (128 more words)Show less

Definition Of Done

  • Every advertised capability has a provider-contract test and at least one malformed/provider-error test.
  • Provider metadata, docs, generated catalog output, and .env.example agree on capabilities and configuration.
  • Events and public errors redact credentials, signed URLs, host-local secrets, and unsafe metadata.
  • Optional-runtime paths degrade to typed skipped/preflight results without installing host-owned packages.

Sharp Edges

SymptomCauseFix
Provider appears in docs with wrong surfaceProviderCapabilities declaration driftedFix adapter capabilities, run provider docs generator, update tests
Optional provider missing from doctorRequired env var absentConfirm variable name from .env.example; do not read .env
Contract helper fails on JSONMetadata/raw payload not JSON-nativeValidate at construction and convert tuples/objects before return
Remote test leaks URL/queryEvent target/message metadata not sanitizedAdd regression in tests/test_observability.py or provider test

© AbdelStark, 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 in .codex/skills/provider-adapter-development of AbdelStark/worldforge.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 30b65da

Compare with similar skills

Provider Adapter Development 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.

Provider Adapter Development compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Provider Adapter Development this skillAbdelStark/worldforge108—~990Automated safety check: NotesMIT
Nx Generatenomcopter/react-mosaic4.8k7 repos~1.9kAutomated safety check: PassCustom licence
PonytailDavidObando/gsharp5648 repos~1.7kAutomated safety check: PassMIT
Run Nx Generatornrwl/nx29k2 repos~592Automated safety check: NotesMIT
Conductor Setupgemini-cli-extensions/conductor3.8k—~4.2kAutomated safety check: PassApache-2.0
Mirage VFS Adapter Authoringstrukto-ai/mirage3.7k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Nx Generate

    nomcopter/react-mosaic

    Generate code using nx generators. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 7 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    564 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Run Nx generators with prioritization for workspace-plugin generators.

    29k GitHub starsUsed in 2 repos~592 tokens
    DevelopmentAuto-check: notes
  • Conductor Setup

    gemini-cli-extensions/conductor

    Scaffolds the project and sets up the Conductor environment.

    3.8k GitHub stars~4.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.

    3.7k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.

    14k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from AbdelStark/worldforge

  • Public Docs Release

    AbdelStark/worldforge

    A skill your agent uses for WorldForge README, docs, changelog, generated provider docs, MkDocs navigation, version/release metadata, public positioning, and release or publish readiness checks.

    108 GitHub stars~679 tokensUpdated 20 days ago
    Auto-check passed
  • Testing Validation

    AbdelStark/worldforge

    A skill your agent uses when selecting, running, or fixing WorldForge validation: pytest, coverage, ruff, generated provider docs, MkDocs strict build, package contract, CI failures, and release…

    108 GitHub stars~871 tokensUpdated 20 days ago
    Auto-check passed
  • Evaluation Benchmarking

    AbdelStark/worldforge

    A skill your agent uses for WorldForge evaluation suites, benchmark harness changes, benchmark input fixtures, budget gates, report rendering, metrics semantics, and any claims based on benchmark or…

    108 GitHub stars~732 tokensUpdated 20 days ago
    Auto-check passed
  • Optional Runtime Smokes

    AbdelStark/worldforge

    A skill your agent uses for LeWorldModel, GR00T, LeRobot, PushT robotics showcase, real-checkpoint smoke scripts, checkpoint building, and host-owned optional runtime dependencies.

    108 GitHub stars~855 tokensUpdated 20 days ago
    Auto-check passed
  • Persistence State

    AbdelStark/worldforge

    A skill your agent uses for WorldForge local state: run workspaces and artifacts under .worldforge/ (run manifests, evidence bundles, retention/prune), the WorldForge(statedir=...) directory, and…

    108 GitHub stars~921 tokensUpdated 20 days ago
    Auto-check passed
  • Tui Development

    AbdelStark/worldforge

    A skill your agent uses for the robotics showcase Textual UI: report panes, launch helpers, screenshots, visual tests, and changes under src/worldforge/harness/tui.py or robotics view/rendering…

    108 GitHub stars~792 tokensUpdated 20 days ago
    Auto-check passed

Categories

Questions about Provider Adapter Development

What does Provider Adapter Development do?

A skill your agent uses for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching…. Provider Adapter Development is an agent skill from AbdelStark/worldforge. Use for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching LeWorldModel, GR00T, LeRobot, Cosmos-Policy, JEPA, Genie, or JEPA-WMS.

When should I use Provider Adapter Development?

Provider Adapter Development fits situations like: worldForge provider work: adding adapters; changing capability declarations; promoting scaffolds; debugging provider failures.

How do I install Provider Adapter Development in Claude Code?

Run `npx skills add AbdelStark/worldforge --skill provider-adapter-development -a claude-code`. Or copy the skill folder (.codex/skills/provider-adapter-development in AbdelStark/worldforge) into .claude/skills/provider-adapter-development in your project. Claude Code loads it when a task matches its description.

How do I install Provider Adapter Development in Codex?

Run `npx skills add AbdelStark/worldforge --skill provider-adapter-development -a codex`. Or copy the skill folder (.codex/skills/provider-adapter-development in AbdelStark/worldforge) into .agents/skills/provider-adapter-development in your project. Codex loads it when a task matches its description.

Can I use Provider Adapter Development 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 AbdelStark/worldforge --skill provider-adapter-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/provider-adapter-development, .gemini/skills/provider-adapter-development, .github/skills/provider-adapter-development and .opencode/skills/provider-adapter-development in your project.

What does Provider Adapter Development need to run?

Going by SKILL.md and its folder, Provider Adapter Development needs the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does Provider Adapter Development access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Provider Adapter Development safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Provider Adapter Development use?

Provider Adapter Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Provider Adapter Development use?

About 990 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Provider Adapter Development?

Skills that share tags, products or a category with Provider Adapter Development: Nx Generate (nomcopter/react-mosaic, 4.8k stars), Ponytail (DavidObando/gsharp, 564 stars), Run Nx Generator (nrwl/nx, 29k stars) and Conductor Setup (gemini-cli-extensions/conductor, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Provider Adapter Development?

AbdelStark (a GitHub user) maintains it in AbdelStark/worldforge, which has 108 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 19, 2026.

Source: AbdelStark/worldforge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.