Agent skill

Background Job Orchestrator

by curiositech in curiositech/some_claude_skills

Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues.

MITAuto-check passedBackend & APIs

Install Background Job Orchestrator

skills CLI
$ npx skills add curiositech/some_claude_skills --skill background-job-orchestrator -a claude-code

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

GitHub CLI
$ gh skill install curiositech/some_claude_skills background-job-orchestrator --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/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/background-job-orchestrator .claude/skills/background-job-orchestrator && 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
background-job-orchestrator
GitHub stars
244
Token cost
~3.2k tokens
SKILL.md length
545 words
Files
5 (incl. scripts, references)
Skills in repo
95
Repo updated
First seen
Licence
MIT

At a glance

Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues.

  • Async task processing
  • SKILL.md covers When to Use, Quick Decision Tree, Technology Selection and Common Anti-Patterns, plus 7 more sections
  • Runs TypeScript and Shell scripts from its folder
  • Email campaigns

What it does

Background Job Orchestrator is an agent skill from curiositech/some_claude_skills. Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ", "Celery". NOT for real-time WebSocket communication, synchronous API calls, or simple setTimeout operations.

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `.claude-plugin/plugin.json`, `references/bullmq-patterns.md` and `scripts/queue_health_check.ts`).

It sits in Backend & APIs, covering Background jobs. It works with Redis. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.

When your agent uses it

  • Async task processing
  • Email campaigns
  • Report generation
  • Batch operations

Example prompts

  • “background job”
  • “async task”
  • “worker”
  • “/background-job-orchestrator”

Requirements

  • Node.js
  • A Bash shell
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*,pip:*)

What it can do on your machine

Read from SKILL.md and the folder at commit 6713fc7. 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:*
    • pip:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (TypeScript and Shell), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

    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

Background Job Orchestrator loads about 3.2k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 545 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 545 words, ~3,234 tokens.

Download SKILL.mdSave it as .claude/skills/background-job-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
background-job-orchestrator
description
Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ", "Celery". NOT for real-time WebSocket communication, synchronous API calls, or simple setTimeout operations.
allowed-tools
Read, Write, Edit, Bash(npm:*,pip:*)
metadata.category
DevOps & Site Reliability
metadata.tags
background, job, orchestrator, background-job, async-task

Background Job Orchestrator

Expert in designing and implementing production-grade background job systems that handle long-running tasks without blocking API responses.

When to Use

✅ Use for:

  • Long-running tasks (email sends, report generation, image processing)
  • Batch operations (bulk imports, exports, data migrations)
  • Scheduled tasks (daily digests, cleanup jobs, recurring reports)
  • Tasks requiring retry logic (external API calls, flaky operations)
  • Priority-based processing (premium users first, critical alerts)
  • Rate-limited operations (API quotas, third-party service limits)

❌ NOT for:

  • Real-time bidirectional communication (use WebSockets)
  • Sub-second latency requirements (use in-memory caching)
  • Simple delays (setTimeout is fine for <5 seconds)
  • Synchronous API responses (keep logic in request handler)

Quick Decision Tree

Does this task:
├── Take &gt;5 seconds? → Background job
├── Need to retry on failure? → Background job
├── Run on a schedule? → Background job (cron pattern)
├── Block user interaction? → Background job
├── Process in batches? → Background job
└── Return immediately? → Keep synchronous

Technology Selection

When to use:

  • TypeScript project
  • Redis already in stack
  • Need advanced features (rate limiting, priorities, repeatable jobs)

Why BullMQ over Bull:

  • Bull (v3) → BullMQ (v4+): Complete rewrite in TypeScript
  • Better Redis connection handling
  • Improved concurrency and performance
  • Active maintenance (Bull is in maintenance mode)
Python: Celery

When to use:

  • Python/Django project
  • Need distributed task execution
  • Complex workflows (chains, groups, chords)

Alternatives:

  • RQ (Redis Queue): Simpler, fewer features
  • Dramatiq: Modern, less ecosystem
  • Huey: Lightweight, good for small projects
Cloud-Native: AWS SQS, Google Cloud Tasks

When to use:

  • Serverless architecture
  • Don't want to manage Redis/RabbitMQ
  • Need guaranteed delivery and dead-letter queues

Common Anti-Patterns

Anti-Pattern 1: No Dead Letter Queue

Novice thinking: "Retry 3 times, then fail silently"

Problem: Failed jobs disappear with no visibility or recovery path.

Correct approach:

typescript
// BullMQ with dead letter queue
const queue = new Queue('email-queue', {
  connection: redis,
  defaultJobOptions: {
    attempts: 3,
    backoff: {
      type: 'exponential',
      delay: 2000
    },
    removeOnComplete: 100, // Keep last 100 successful
    removeOnFail: false     // Keep all failed for inspection
  }
});

// Monitor failed jobs
const failedJobs = await queue.getFailed();

Timeline:

  • Pre-2020: Retry and forget
  • 2020+: Dead letter queues standard
  • 2024+: Observability for job failures required

Anti-Pattern 2: Synchronous Job Processing

Symptom: API endpoint waits for job completion

Problem:

typescript
// ❌ WRONG - Blocks API response
app.post('/send-email', async (req, res) => {
  await sendEmail(req.body.to, req.body.subject);
  res.json({ success: true });
});

Why wrong: Timeout, poor UX, wastes server resources

Correct approach:

typescript
// ✅ RIGHT - Queue and return immediately
app.post('/send-email', async (req, res) => {
  const job = await emailQueue.add('send', {
    to: req.body.to,
    subject: req.body.subject
  });

  res.json({
    success: true,
    jobId: job.id,
    status: 'queued'
  });
});

// Separate worker processes the job
worker.process('send', async (job) => {
  await sendEmail(job.data.to, job.data.subject);
});

Anti-Pattern 3: No Idempotency

Problem: Job runs twice → duplicate charges, double emails

Why it happens:

  • Redis connection drops mid-processing
  • Worker crashes before job completion
  • Job timeout triggers retry while still running

Correct approach:

typescript
// ✅ Idempotent job with deduplication key
await queue.add('charge-payment', {
  userId: 123,
  amount: 50.00
}, {
  jobId: `payment-${orderId}`, // Prevents duplicates
  attempts: 3
});

// In worker: Check if already processed
worker.process('charge-payment', async (job) => {
  const { userId, amount } = job.data;

  // Check idempotency
  const existing = await db.payments.findOne({
    jobId: job.id
  });
  if (existing) {
    return existing; // Already processed
  }

  // Process payment
  const result = await stripe.charges.create({...});

  // Store idempotency record
  await db.payments.create({
    jobId: job.id,
    result
  });

  return result;
});

Anti-Pattern 4: No Rate Limiting

Problem: Overwhelm third-party APIs or exhaust quotas

Symptom: "Rate limit exceeded" errors from Sendgrid, Stripe, etc.

Correct approach:

typescript
// BullMQ rate limiting
const queue = new Queue('api-calls', {
  limiter: {
    max: 100,        // Max 100 jobs
    duration: 60000  // Per 60 seconds
  }
});

// Or: Priority-based rate limits
await queue.add('send-email', data, {
  priority: user.isPremium ? 1 : 10,
  rateLimiter: {
    max: user.isPremium ? 1000 : 100,
    duration: 3600000 // Per hour
  }
});

Show full SKILL.md (214 more words)Show less
Anti-Pattern 5: Forgetting Worker Scaling

Problem: Single worker can't keep up with queue depth

Symptom: Queue backs up, jobs delayed hours/days

Correct approach:

typescript
// Horizontal scaling with multiple workers
const worker = new Worker('email-queue', async (job) => {
  await processEmail(job.data);
}, {
  connection: redis,
  concurrency: 5  // Process 5 jobs concurrently per worker
});

// Run multiple worker processes (PM2, Kubernetes, etc.)
// Each worker processes concurrency * num_workers jobs

Monitoring:

typescript
// Set up alerts for queue depth
setInterval(async () => {
  const waiting = await queue.getWaitingCount();
  if (waiting > 1000) {
    alert('Queue depth exceeds 1000, scale workers!');
  }
}, 60000);

Implementation Patterns

Pattern 1: Email Campaigns
typescript
// Queue setup
const emailQueue = new Queue('email-campaign', { connection: redis });

// Enqueue batch
async function sendCampaign(userIds: number[], template: string) {
  const jobs = userIds.map(userId => ({
    name: 'send',
    data: { userId, template },
    opts: {
      attempts: 3,
      backoff: { type: 'exponential', delay: 5000 }
    }
  }));

  await emailQueue.addBulk(jobs);
}

// Worker with retry logic
const worker = new Worker('email-campaign', async (job) => {
  const { userId, template } = job.data;

  const user = await db.users.findById(userId);
  const email = renderTemplate(template, user);

  try {
    await sendgrid.send({
      to: user.email,
      subject: email.subject,
      html: email.body
    });
  } catch (error) {
    if (error.code === 'ECONNREFUSED') {
      throw error; // Retry
    }
    // Invalid email, don't retry
    console.error(`Invalid email for user ${userId}`);
  }
}, {
  connection: redis,
  concurrency: 10
});
Pattern 2: Scheduled Reports
typescript
// Daily report at 9 AM
await queue.add('daily-report', {
  type: 'sales',
  recipients: ['admin@company.com']
}, {
  repeat: {
    pattern: '0 9 * * *', // Cron syntax
    tz: 'America/New_York'
  }
});

// Worker generates and emails report
worker.process('daily-report', async (job) => {
  const { type, recipients } = job.data;

  const data = await generateReport(type);
  const pdf = await createPDF(data);

  await emailQueue.add('send', {
    to: recipients,
    subject: `Daily ${type} Report`,
    attachments: [{ filename: 'report.pdf', content: pdf }]
  });
});
Pattern 3: Video Transcoding Pipeline
typescript
// Multi-stage job with progress tracking
await videoQueue.add('transcode', {
  videoId: 123,
  formats: ['720p', '1080p', '4k']
}, {
  attempts: 2,
  timeout: 3600000 // 1 hour timeout
});

worker.process('transcode', async (job) => {
  const { videoId, formats } = job.data;

  for (let i = 0; i < formats.length; i++) {
    const format = formats[i];

    // Update progress
    await job.updateProgress((i / formats.length) * 100);

    // Transcode
    await ffmpeg.transcode(videoId, format);
  }

  await job.updateProgress(100);
});

// Client polls for progress
app.get('/videos/:id/status', async (req, res) => {
  const job = await queue.getJob(req.params.jobId);
  res.json({
    state: await job.getState(),
    progress: job.progress
  });
});

Monitoring & Observability

Essential Metrics
typescript
// Queue health dashboard
async function getQueueMetrics() {
  const [waiting, active, completed, failed, delayed] = await Promise.all([
    queue.getWaitingCount(),
    queue.getActiveCount(),
    queue.getCompletedCount(),
    queue.getFailedCount(),
    queue.getDelayedCount()
  ]);

  return {
    waiting,    // Jobs waiting to be processed
    active,     // Jobs currently processing
    completed,  // Successfully completed
    failed,     // Failed after retries
    delayed,    // Scheduled for future
    health: waiting < 1000 && failed < 100 ? 'healthy' : 'degraded'
  };
}
BullMQ Board (UI)
typescript
// Development: Monitor jobs visually
import { createBullBoard } from '@bull-board/api';
import { BullMQAdapter } from '@bull-board/api/bullMQAdapter';
import { ExpressAdapter } from '@bull-board/express';

const serverAdapter = new ExpressAdapter();

createBullBoard({
  queues: [
    new BullMQAdapter(emailQueue),
    new BullMQAdapter(videoQueue)
  ],
  serverAdapter
});

app.use('/admin/queues', serverAdapter.getRouter());
// Visit http://localhost:3000/admin/queues

Production Checklist

□ Dead letter queue configured
□ Retry strategy with exponential backoff
□ Job timeout limits set
□ Rate limiting for third-party APIs
□ Idempotency keys for critical operations
□ Worker concurrency tuned (CPU cores * 2)
□ Horizontal scaling configured (multiple workers)
□ Queue depth monitoring with alerts
□ Failed job inspection workflow
□ Job data doesn't contain PII in logs
□ Redis persistence enabled (AOF or RDB)
□ Graceful shutdown handling (SIGTERM)

When to Use vs Avoid

ScenarioUse Background Jobs?
Send welcome email on signup✅ Yes - can take 2-5 seconds
Charge credit card⚠️ Maybe - depends on payment provider latency
Generate PDF report (30 seconds)✅ Yes - definitely background
Fetch user profile from DB❌ No - milliseconds, keep synchronous
Process video upload (5 minutes)✅ Yes - always background
Validate form input❌ No - synchronous validation
Daily cron job✅ Yes - use repeatable jobs
Real-time chat message❌ No - use WebSockets

Technology Comparison

FeatureBullMQCeleryAWS SQS
LanguageNode.jsPythonAny (HTTP API)
BackendRedisRedis/RabbitMQ/SQSManaged
Priorities✅✅✅
Rate Limiting✅❌✅ (via attributes)
Repeat/Cron✅✅ (celery-beat)❌ (use EventBridge)
UI DashboardBull BoardFlowerCloudWatch
Workflows❌✅ (chains, groups)❌
Learning CurveMediumMediumLow
CostRedis hostingRedis hosting$0.40/million requests

References

  • /references/bullmq-patterns.md - Advanced BullMQ patterns and examples
  • /references/celery-workflows.md - Celery chains, groups, and chords
  • /references/job-observability.md - Monitoring, alerting, and debugging

Scripts

  • scripts/setup_bullmq.sh - Initialize BullMQ with Redis
  • scripts/queue_health_check.ts - Queue metrics dashboard
  • scripts/retry_failed_jobs.ts - Bulk retry failed jobs

This skill guides: Background job implementation | Queue architecture | Retry strategies | Worker scaling | Job observability

© curiositech, 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 (scripts, references) in .claude/skills/background-job-orchestrator of curiositech/some_claude_skills.

  • SKILL.md
  • .claude-plugin/plugin.json
  • references/bullmq-patterns.md
  • scripts/queue_health_check.ts
  • scripts/setup_bullmq.sh

Open the folder on GitHubat commit 6713fc7

Compare with similar skills

Background Job Orchestrator 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.

Background Job Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Background Job Orchestrator this skillcuriositech/some_claude_skills244—~3.2kAutomated safety check: PassMIT
FoundatioFoundatioFx/Foundatio2.1k—~3.9kAutomated safety check: PassApache-2.0
Schkedbibendi/schked138—~454Automated safety check: PassMIT
Agent Signal Pipelinelobehub/lobehub83k—~1.7kAutomated safety check: PassCustom licence
AsyncTheBeardedBearSAS/claude-craft107—~741Automated safety check: PassMIT
Bullmq Specialistdavila7/claude-code-templates33k5 repos~383Automated safety check: PassMIT

Similar skills

  • Foundatio

    FoundatioFx/Foundatio

    A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.

    2.1k GitHub stars~3.9k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Schked

    bibendi/schked

    Guide for working with Schked, a Ruby recurring-job scheduler built on top of rufus-scheduler.

    138 GitHub stars~454 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Agent Signal Pipeline

    lobehub/lobehub

    Guides building event-driven background work for LobeHub agents, with sources, signals, actions, policies, workflow handoff and deduplication.

    83k GitHub stars~1.7k tokensUpdated today
    Backend & APIsAuto-check passed
  • Async

    TheBeardedBearSAS/claude-craft

    Architecture async-first avec messaging et queues (Symfony Messenger, Laravel Queue, Ecotone).

    107 GitHub stars~741 tokensUpdated 26 days ago
    Backend & APIsAuto-check passed
  • Bullmq Specialist

    davila7/claude-code-templates

    BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications.

    33k GitHub starsUsed in 5 repos~383 tokens
    Backend & APIsAuto-check passed
  • Bullmq Specialist

    sickn33/agentic-awesome-skills

    BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications.

    47k GitHub starsUsed in 2 repos~2.5k tokens
    Backend & APIsAuto-check passed

More from curiositech/some_claude_skills

All 95 skills in this repo
  • Crisis Detection Intervention AI

    curiositech/some_claude_skills

    Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.

    244 GitHub starsUsed in 2 repos~3.8k tokens
    Auto-check passed
  • Form Validation Architect

    curiositech/some_claude_skills

    End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.

    244 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed
  • GitHub Actions Pipeline Builder

    curiositech/some_claude_skills

    Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.

    244 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check: notes
  • Competitive Cartographer

    curiositech/some_claude_skills

    Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.

    244 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Computer Vision Pipeline

    curiositech/some_claude_skills

    Build production computer vision pipelines for object detection, tracking, and video analysis.

    244 GitHub stars~4k tokensUpdated 1 mo ago
    Auto-check passed
  • Design Archivist

    curiositech/some_claude_skills

    Long-running design anthropologist that builds comprehensive visual databases from 500-1000 real-world examples, extracting color palettes, typography patterns, layout systems, and interaction…

    244 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Background Job Orchestrator

What does Background Job Orchestrator do?

Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Background Job Orchestrator is an agent skill from curiositech/some_claude_skills. Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues.

When should I use Background Job Orchestrator?

Background Job Orchestrator fits situations like: async task processing; email campaigns; report generation; batch operations.

How do I install Background Job Orchestrator in Claude Code?

Run `npx skills add curiositech/some_claude_skills --skill background-job-orchestrator -a claude-code`. Or copy the skill folder (.claude/skills/background-job-orchestrator in curiositech/some_claude_skills) into .claude/skills/background-job-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Background Job Orchestrator in Codex?

Run `npx skills add curiositech/some_claude_skills --skill background-job-orchestrator -a codex`. Or copy the skill folder (.claude/skills/background-job-orchestrator in curiositech/some_claude_skills) into .agents/skills/background-job-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Background Job Orchestrator 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 curiositech/some_claude_skills --skill background-job-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/background-job-orchestrator, .gemini/skills/background-job-orchestrator, .github/skills/background-job-orchestrator and .opencode/skills/background-job-orchestrator in your project.

What does Background Job Orchestrator need to run?

Going by SKILL.md and its folder, Background Job Orchestrator needs TypeScript and a shell for the scripts in its folder. Our summary lists: Node.js; A Bash shell. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*,pip:*).

Does Background Job Orchestrator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Background Job Orchestrator 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Background Job Orchestrator use?

Background Job Orchestrator 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 Background Job Orchestrator use?

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

What are the alternatives to Background Job Orchestrator?

Skills that share tags, products or a category with Background Job Orchestrator: Foundatio (FoundatioFx/Foundatio, 2.1k stars), Schked (bibendi/schked, 138 stars), Agent Signal Pipeline (lobehub/lobehub, 83k stars) and Async (TheBeardedBearSAS/claude-craft, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Background Job Orchestrator?

curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 244 GitHub stars. The repository holds 95 skills in this directory. The repository was last updated on September 6, 2026.

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