Agent skill

Sentry Migration Deep Dive

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

Migrate to Sentry from other error tracking tools like Rollbar, Bugsnag, or New Relic.

MITAuto-check: notesDevOps & Cloud

Install Sentry Migration Deep Dive

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-migration-deep-dive -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-migration-deep-dive --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/sentry-migration-deep-dive .claude/skills/sentry-migration-deep-dive && 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
sentry-migration-deep-dive
GitHub stars
2.8k
Token cost
~2.6k tokens
SKILL.md length
707 words
Files
5 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Migrate to Sentry from other error tracking tools like Rollbar, Bugsnag, or New Relic.

  • Works in 3 steps: Map Concepts Between Providers → Install Sentry in Parallel → Migrate Alert Rules, Validate Parity,…
  • Replacing an existing error tracker with Sentry
  • SKILL.md covers Overview, Current State, Prerequisites and Instructions, plus 5 more sections
  • Calls npm, curl and jq; reaches sentry.io and api.rollbar.com; needs ROLLBAR_TOKEN and SENTRY_AUTH_TOKEN

What it does

Sentry Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate to Sentry from other error tracking tools like Rollbar, Bugsnag, or New Relic. Use when replacing an existing error tracker with Sentry, running tools in parallel during a transition, or mapping API calls between providers. Trigger with phrases like "migrate to sentry", "switch from rollbar to sentry", "replace bugsnag with sentry", "sentry migration plan".

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/errors.md`, `references/examples.md` and `references/migration-from-bugsnag.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Monitoring and alerting. It works with Sentry and New Relic. 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

  • Replacing an existing error tracker with Sentry
  • Running tools in parallel during a transition
  • Mapping API calls between providers
  • With phrases like migrate to sentry

Example prompts

  • “migrate to sentry”
  • “switch from rollbar to sentry”
  • “replace bugsnag with sentry”
  • “/sentry-migration-deep-dive”

Requirements

  • A credential in ROLLBAR_TOKEN
  • A credential in SENTRY_AUTH_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(node:*), Grep, Glob

Workflow steps

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

  1. Map Concepts Between Providers
  2. Install Sentry in Parallel
  3. Migrate Alert Rules, Validate Parity, and Cut Over

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:*)
    • Bash(npx:*)
    • Bash(node:*)
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • curl
    • jq

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • sentry.io
    • api.rollbar.com

    Also links to:

    • docs.sentry.io

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

  • Credentials

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

    • ROLLBAR_TOKEN
    • SENTRY_AUTH_TOKEN

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

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Sentry Migration Deep Dive loads about 2.6k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 707 words of instructions outside code blocks.

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

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:165
    un grep across all file types including `.env`, CI configs, and infrastructure-as-code |

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). 707 words, ~2,577 tokens.

Download SKILL.mdSave it as .claude/skills/sentry-migration-deep-dive/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
sentry-migration-deep-dive
description
Migrate to Sentry from other error tracking tools like Rollbar, Bugsnag, or New Relic. Use when replacing an existing error tracker with Sentry, running tools in parallel during a transition, or mapping API calls between providers. Trigger with phrases like "migrate to sentry", "switch from rollbar to sentry", "replace bugsnag with sentry", "sentry migration plan".
allowed-tools
Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(node:*), Grep, Glob
compatibility
Designed for Claude Code
version
1.51.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, sentry, migration, rollbar, bugsnag, new-relic, error-tracking

Sentry Migration Deep Dive

Overview

Replace an existing error tracking tool (Rollbar, Bugsnag, New Relic, Raygun, Airbrake) with Sentry using a phased migration that runs both tools in parallel before cutover. This skill covers concept mapping between providers, SDK swap patterns, alert rule migration, team training, and rollback strategy.

Current State

!npm list 2>/dev/null | command grep -iE "sentry|rollbar|bugsnag|raygun|airbrake|honeybadger|newrelic" || echo 'No error tracking packages found'

Prerequisites

  • Admin access to the current error tracking tool (API keys, alert rule access)
  • Sentry project created with DSN available in environment variables
  • Source maps or debug symbols configured for stack trace resolution
  • Parallel run timeline agreed with team (2-4 weeks recommended)
  • Inventory of current alert rules, integrations, and custom filters

Instructions

Step 1: Map Concepts Between Providers

Build a translation table mapping the current tool's terminology and API surface to Sentry equivalents. Scan the codebase for all calls to the existing SDK.

ConceptRollbarBugsnagNew RelicSentry
Capture errorrollbar.error(err)Bugsnag.notify(err)newrelic.noticeError(err)Sentry.captureException(err)
Log messagerollbar.info(msg)Bugsnag.notify(msg)newrelic.recordCustomEvent()Sentry.captureMessage(msg)
User contextrollbar.configure({ person: {...} })Bugsnag.setUser(id, email)newrelic.setUserID(id)Sentry.setUser({ id, email })
Tags/metadatarollbar.configure({ custom: {...} })bugsnag.addMetadata(tab, data)newrelic.addCustomAttributes()Sentry.setTag() / Sentry.setContext()
Breadcrumbsrollbar.log(level, msg)Bugsnag.leaveBreadcrumb(msg)N/ASentry.addBreadcrumb({ message })
Release trackingcode_version configappVersion configNEW_RELIC_LABELSSentry.init({ release: 'v1.2.3' })
Environmentenvironment configreleaseStage configNEW_RELIC_APP_NAME suffixSentry.init({ environment: 'prod' })
Error filtercheckIgnore callbackonError callbackignore_errors configbeforeSend hook
PerformanceN/A@bugsnag/plugin-*Built-in APMBuilt-in tracesSampleRate

Use Grep to find all references: grep -rn "rollbar\|Bugsnag\|newrelic\|noticeError" --include="*.ts" --include="*.js" src/

Step 2: Install Sentry in Parallel

Install the Sentry SDK alongside the existing tool. Route errors to both destinations during the transition period to validate parity before removing the old tool.

typescript
// instrument.ts -- load BEFORE any other import
import * as Sentry from '@sentry/node';

Sentry.init({
  dsn: process.env.SENTRY_DSN,
  environment: process.env.NODE_ENV,
  release: process.env.npm_package_version,  // auto-read from package.json
  tracesSampleRate: 0.1,                     // start low, tune after baseline
  sendDefaultPii: false,
});
typescript
// dual-reporter.ts -- send to BOTH tools during parallel run
import * as Sentry from '@sentry/node';

// Keep existing tool import (e.g., Rollbar, Bugsnag)
import Rollbar from 'rollbar';
const rollbar = new Rollbar({ accessToken: process.env.ROLLBAR_TOKEN });

export function captureError(error: Error, context?: Record<string, unknown>) {
  // Sentry (new)
  Sentry.withScope((scope) => {
    if (context) scope.setContext('migration', context);
    Sentry.captureException(error);
  });

  // Old tool (keep running until parity verified)
  rollbar.error(error, context);
}

export function setUserContext(user: { id: string; email?: string }) {
  Sentry.setUser(user);
  rollbar.configure({ payload: { person: { id: user.id, email: user.email } } });
}
Step 3: Migrate Alert Rules, Validate Parity, and Cut Over
  1. Export alert rules from the old tool. Map each alert to a Sentry equivalent:

    • "New error in production" becomes a Sentry Issue Alert with filter environment:production and action "Send Slack notification".
    • "Error rate > 100/min" becomes a Sentry Metric Alert with threshold 100 events per minute and PagerDuty action.
    • Rate-based alerts use Sentry Metric Alerts; occurrence-based alerts use Sentry Issue Alerts.
  2. Validate parity during the parallel run window:

    bash
    # Compare error counts -- Sentry API
    curl -s -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
      "https://sentry.io/api/0/projects/$SENTRY_ORG/$SENTRY_PROJECT/stats/" | jq '.[] | .total'
    
    # Compare with old tool API (Rollbar example)
    curl -s -H "X-Rollbar-Access-Token: $ROLLBAR_TOKEN" \
      "https://api.rollbar.com/api/1/reports/top_recent_items" | jq '.result | length'
    • Error count should be within 10% between tools.
    • Stack traces must resolve correctly (verify source maps uploaded to Sentry).
    • Breadcrumbs, user context, and tags must appear in Sentry event detail.
  3. Remove the old SDK after parity is confirmed:

    bash
    npm uninstall rollbar @bugsnag/node @bugsnag/plugin-express newrelic || echo "Some packages not found (expected if only one tool was installed)"

    Search for leftover references and remove them:

    bash
    grep -rn "rollbar\|bugsnag\|newrelic\|raygun\|airbrake" \
      --include="*.ts" --include="*.js" --include="*.env*" \
      --exclude-dir=node_modules . || echo "No remaining references found"
  4. Schedule team training: walk through the Sentry dashboard (Issues, Performance, Releases views), show how to assign issues, and demonstrate the alert configuration UI.

  5. Rollback strategy: keep the old tool's npm package in devDependencies and its configuration file in a migration-backup/ directory for 30 days after cutover. If Sentry surfaces fewer errors than expected, re-enable dual reporting and investigate.

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

Output

  • Concept mapping table translating old API calls to Sentry equivalents
  • Dual-reporting wrapper sending errors to both tools during parallel run
  • Sentry SDK initialized with environment, release, and sampling configuration
  • Alert rules migrated from old tool to Sentry Issue and Metric Alerts
  • Parity validation confirming error count, stack traces, and context match
  • Old SDK removed and all references cleaned from codebase

Error Handling

ErrorCauseSolution
Error count mismatch between toolsDifferent sampling rates or filter rulesSet both tools to 100% sampling during parallel run; disable beforeSend filters temporarily
Missing stack traces in SentrySource maps not uploadedRun sentry-cli sourcemaps upload --release=$(npm pkg get version) in CI
Old tool references remain after removalIncomplete codebase searchRun grep across all file types including .env, CI configs, and infrastructure-as-code
Sentry alerts not firingAlert conditions misconfiguredTest with a synthetic error: Sentry.captureException(new Error('alert-test')) and verify delivery
New Relic APM data missing after switchSentry replaces error tracking only, not full APMKeep New Relic for APM if needed; Sentry Performance covers traces but not infrastructure metrics
Team unfamiliar with Sentry UINo training providedSchedule 30-minute walkthrough covering Issues, Performance, and Releases views

Examples

Migrate Express app from Rollbar to Sentry:

typescript
// BEFORE: rollbar error handler middleware
import Rollbar from 'rollbar';
const rollbar = new Rollbar({ accessToken: process.env.ROLLBAR_TOKEN });
app.use(rollbar.errorHandler());

// AFTER: Sentry error handler middleware
import * as Sentry from '@sentry/node';
Sentry.init({ dsn: process.env.SENTRY_DSN });
Sentry.setupExpressErrorHandler(app);

Migrate React error boundary from Bugsnag to Sentry:

typescript
// BEFORE: Bugsnag React initialization + error boundary
import Bugsnag from '@bugsnag/js';
import BugsnagPluginReact from '@bugsnag/plugin-react';
Bugsnag.start({ plugins: [new BugsnagPluginReact()] });
const ErrorBoundary = Bugsnag.getPlugin('react')!.createErrorBoundary(React);
// Usage: wrap root component with ErrorBoundary

// AFTER: Sentry React initialization + error boundary
import * as Sentry from '@sentry/react';
Sentry.init({ dsn: process.env.SENTRY_DSN });
// Usage: wrap root component with Sentry.ErrorBoundary (accepts fallback prop)
// See @sentry/react docs for ErrorBoundary component API

Post-migration verification script:

typescript
import * as Sentry from '@sentry/node';

async function verifyMigration() {
  const eventId = Sentry.captureException(new Error('Migration verification test'));
  console.log('Error captured:', eventId ? 'PASS' : 'FAIL');

  Sentry.captureMessage('Migration complete', 'info');

  const flushed = await Sentry.flush(5000);
  console.log('Events delivered:', flushed ? 'PASS' : 'FAIL');
}

verifyMigration();

Resources

Next Steps

After migration, proceed to sentry-performance-tracing to configure distributed tracing, or sentry-prod-checklist to verify production readiness.

© 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 4 other files (references) in skills/.curated/sentry-migration-deep-dive of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/errors.md
  • references/examples.md
  • references/migration-from-bugsnag.md
  • references/migration-from-rollbar.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Sentry Migration Deep Dive 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.

Sentry Migration Deep Dive compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sentry Migration Deep Dive this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.6kAutomated safety check: NotesMIT
Sentry Miniapp SDKlizhiyao/sentry-miniapp687—~2.1kAutomated safety check: PassMIT
Cross Source Correlationaozyildirim/Agena103—~756Automated safety check: PassMIT
Superset Incident Triagesuperset-sh/superset15k—~1kAutomated safety check: PassCustom licence
Ops MonitorLifecycle-Innovations-Limited/claude-ops5421 repos~1.5kAutomated safety check: NotesMIT
Sentry Alert TunerLeoYeAI/openclaw-master-skills2.2k—~7.3kAutomated safety check: PassMIT

Similar skills

  • Sentry Miniapp SDK

    lizhiyao/sentry-miniapp

    Set up or troubleshoot Sentry error monitoring, tracing, offline cache and source maps in native mini programs, Taro or uni-app.

    687 GitHub stars~2.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Cross Source Correlation

    aozyildirim/Agena

    Correlate near-in-time events across PR merges, deploys, monitoring (Sentry/NewRelic/Datadog/AppDynamics) and ticket trackers (Jira/Azure DevOps) into confidence-scored clusters that answer "which…

    103 GitHub stars~756 tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Superset Incident Triage

    superset-sh/superset

    Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.

    15k GitHub stars~1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Ops Monitor

    Lifecycle-Innovations-Limited/claude-ops

    OPS on-demand: This skill should be used when the user asks to "datadog", "APM alerts", or…

    542 GitHub starsUsed in 1 repo~1.5k tokens
    DevOps & CloudAuto-check: notes
  • Sentry Alert Tuner

    LeoYeAI/openclaw-master-skills

    Reduce Sentry alert fatigue by surgically tuning issue grouping, fingerprint rules, severity mapping, sample rates, before-send filters, sourcemap pipelines, and release-health gates.

    2.2k GitHub stars~7.3k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Newrelic CLI Alerts

    Kilo-Org/kilo-marketplace

    This subskill should be used when managing New Relic alert policies, APM or NRQL conditions, notification channels, or open incidents with the New Relic CLI.

    190 GitHub stars~664 tokensUpdated 12 days ago
    DevOps & CloudAuto-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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Works with

Categories

Questions about Sentry Migration Deep Dive

What does Sentry Migration Deep Dive do?

Migrate to Sentry from other error tracking tools like Rollbar, Bugsnag, or New Relic. Sentry Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate to Sentry from other error tracking tools like Rollbar, Bugsnag, or New Relic.

When should I use Sentry Migration Deep Dive?

Sentry Migration Deep Dive fits situations like: replacing an existing error tracker with Sentry; running tools in parallel during a transition; mapping API calls between providers; with phrases like migrate to sentry.

How do I install Sentry Migration Deep Dive in Claude Code?

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

How do I install Sentry Migration Deep Dive in Codex?

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

Can I use Sentry Migration Deep Dive 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 sentry-migration-deep-dive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-migration-deep-dive, .gemini/skills/sentry-migration-deep-dive, .github/skills/sentry-migration-deep-dive and .opencode/skills/sentry-migration-deep-dive in your project.

What does Sentry Migration Deep Dive need to run?

Going by SKILL.md and its folder, Sentry Migration Deep Dive needs the command-line tools its instructions call (npm, curl and jq) and credentials named ROLLBAR_TOKEN and SENTRY_AUTH_TOKEN. Our summary lists: A credential in ROLLBAR_TOKEN; A credential in SENTRY_AUTH_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(node:*), Grep, Glob. Compatibility (from SKILL.md): Designed for Claude Code.

Does Sentry Migration Deep Dive access the network?

SKILL.md names 3 domains. In commands or code: sentry.io and api.rollbar.com; the agent is likely to contact these when it follows the instructions. As links in the text: docs.sentry.io. This is read from the text; nothing was executed.

Is Sentry Migration Deep Dive 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 Sentry Migration Deep Dive use?

Sentry Migration Deep Dive 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 Sentry Migration Deep Dive use?

About 2.6k tokens (SKILL.md is roughly 10k 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 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Sentry Migration Deep Dive?

Skills that share tags, products or a category with Sentry Migration Deep Dive: Sentry Miniapp SDK (lizhiyao/sentry-miniapp, 687 stars), Cross Source Correlation (aozyildirim/Agena, 103 stars), Superset Incident Triage (superset-sh/superset, 15k stars) and Ops Monitor (Lifecycle-Innovations-Limited/claude-ops, 542 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sentry Migration Deep Dive?

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.