skills.rest
cill-i-am
cill-i-amCOMMUNITY
Explore all skills by this author →
𝕏@cillo_bGitHub

devtools-marketplace

Automate listing and registering third-party plugins in the TanStack Devtools Marketplace.

Updated Apr 1, 2026
Search Tags:#npm#plugin#devtools#registry#marketplace#pr#publisher
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill devtools-marketplace-cill-i-am
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devtools-marketplace
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/tanstack-devtools-marketplace
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill devtools-marketplace-cill-i-am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of publishing third-party TanStack Devtools plugins and submitting them for inclusion in the official marketplace.

Core Features & Use Cases

  • Defines the required registry entry fields (packageName, title, framework, requires, pluginImport, etc.) and the workflow to prepare a PR against TanStack/devtools.
  • Documents the PR submission process and the integration steps to wire a plugin into the marketplace so users can install it from npm.
  • Provides guidance for maintaining metadata, docs, and repository references to ensure long-term compatibility.

Quick Start

Publish your plugin to npm and submit a PR to TanStack/devtools to add your plugin to the marketplace.

Frequently Asked Questions about devtools-marketplace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a plugin to the TanStack Devtools Marketplace?▼

Publishing a plugin to the TanStack Devtools Marketplace requires preparing a registry entry with packageName, title, framework, requires, pluginImport, repoUrl, and docsUrl, then submitting a PR to the TanStack/devtools repository.

What metadata fields are required for a TanStack Devtools plugin registry entry?▼

Required registry entry fields for a TanStack Devtools plugin include packageName, title, framework, requires.minVersion, pluginImport, repoUrl, and docsUrl to ensure proper marketplace integration and long-term compatibility.

Do I need to publish my TanStack plugin to npm before submitting a marketplace PR?▼

Publishing your plugin to npm is necessary before submitting a PR to the TanStack Devtools Marketplace, because the registry entry references the packageName to allow users to install the plugin directly from npm.

What is the PR workflow for adding a plugin to the TanStack devtools registry?▼

The PR workflow involves defining the required registry metadata fields, documenting the plugin, wiring the integration steps, and submitting a pull request against the TanStack/devtools repository for the team to review.

How do I maintain long-term compatibility for a TanStack Devtools marketplace plugin?▼

Maintaining long-term compatibility for a TanStack Devtools marketplace plugin involves keeping the registry metadata, docsUrl, and repoUrl references updated to match the requires.minVersion framework requirements.

Can I submit a third-party plugin to the TanStack Devtools Marketplace without a docsUrl?▼

Submitting a third-party plugin to the TanStack Devtools Marketplace requires a docsUrl and repoUrl in the registry entry to ensure proper documentation and repository references for the integration PR.

Related Skills

Explore More Software Engineering Skills→
baekenoughbaekenough
34

npm-publish

Automate npm package publishing with pre-publish validation and dry-run checks.

Community
Advanced
TanStackTanStack
485

devtools-marketplace

Publish third-party plugins to the TanStack Devtools Marketplace via PluginMetadata and PR submission.

Official
Intermediate
patricio0312revpatricio0312rev
5

release-automation-builder

Automate npm package release workflows with changesets or semantic-release.

Community
Advanced
EthanAlgoXEthanAlgoX
65

clawhub

Search and install third-party agent skills from the ClawHub registry via npx.

Community
Basic