OmniRoute Backup and Sync CLI
diegosouzapw/OmniRoute
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
Agent skill
Planning Disaster Recovery
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Execute use when you need to work with backup and recovery. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Install Planning Disaster Recovery
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace planning-disaster-recovery --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/planning-disaster-recovery .claude/skills/planning-disaster-recovery && rm -rf skills-srcUse ~/.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/
Install the "planning-disaster-recovery" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/planning-disaster-recovery into .claude/skills/planning-disaster-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-disaster-recovery", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/planning-disaster-recoveryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace planning-disaster-recovery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/planning-disaster-recovery .agents/skills/planning-disaster-recovery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning-disaster-recovery" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/planning-disaster-recovery into .agents/skills/planning-disaster-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-disaster-recovery", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace planning-disaster-recovery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/planning-disaster-recovery .cursor/skills/planning-disaster-recovery && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "planning-disaster-recovery" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/planning-disaster-recovery into .cursor/skills/planning-disaster-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-disaster-recovery", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/planning-disaster-recovery--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace planning-disaster-recovery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/planning-disaster-recovery .gemini/skills/planning-disaster-recovery && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "planning-disaster-recovery" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/planning-disaster-recovery into .gemini/skills/planning-disaster-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-disaster-recovery", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace planning-disaster-recoveryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/planning-disaster-recovery .github/skills/planning-disaster-recovery && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "planning-disaster-recovery" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/planning-disaster-recovery into .github/skills/planning-disaster-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-disaster-recovery", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace planning-disaster-recovery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/planning-disaster-recovery .opencode/skills/planning-disaster-recovery && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "planning-disaster-recovery" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/planning-disaster-recovery into .opencode/skills/planning-disaster-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-disaster-recovery", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
planning-disaster-recovery- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 509 words
- Files
- 4 (incl. scripts, references, assets)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Execute use when you need to work with backup and recovery. An agent skill from jeremylongshore/tons-of-skills-marketplace.
- Works in 10 steps: Catalog all production services with… → Map dependencies between services to… → Design the DR strategy per tier:… → …
- You need to work with backup and recovery
- SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
- With phrases like create backups
What it does
Planning Disaster Recovery is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute use when you need to work with backup and recovery. This skill provides backup automation and disaster recovery with comprehensive guidance and automation. Trigger with phrases like "create backups", "automate backups", or "implement disaster recovery".
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Backup and disaster recovery. 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
- You need to work with backup and recovery
- With phrases like create backups
- Automate backups
- Implement disaster recovery
Example prompts
- “create backups”
- “automate backups”
- “implement disaster recovery”
- “/planning-disaster-recovery”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(tar:*), Bash(rsync:*), Bash(aws:s3:*)
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Catalog all production services with their criticality tier (Tier 1: < 15 min RTO, Tier 2: < 1 hour, Tier 3: < 24 hours)
- Map dependencies between services to identify single points of failure and cascading failure paths
- Design the DR strategy per tier: active-active for Tier 1, pilot light or warm standby for Tier 2, backup-restore for Tier 3
- Generate Terraform for standby region infrastructure: VPC, subnets, security groups, and scaled-down compute
- Configure database replication: RDS cross-region read replicas, DynamoDB global tables, or Cloud SQL cross-region replicas
- Set up DNS failover using Route 53 health checks, Cloud DNS routing policies, or global load balancers
- Create automated failover scripts: promote read replica to primary, update DNS records, scale up standby compute
- Document the DR runbook with step-by-step procedures, responsible parties, and communication plans
- Schedule quarterly DR drills: simulate region failure, execute the runbook, measure actual RTO/RPO, and document gaps
- Set up monitoring for replication lag, backup freshness, and standby infrastructure health
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:
ReadWriteEditGrepGlobBash(tar:*)Bash(rsync:*)Bash(aws:s3:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.aws.amazon.comcloud.google.comlearn.microsoft.com
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.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Planning Disaster Recovery loads about 1.2k tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 72 tokens; SKILL.md has 509 words of instructions outside code blocks.
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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 509 words, ~1,154 tokens.
Download SKILL.mdSave it as
.claude/skills/planning-disaster-recovery/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- planning-disaster-recovery
- description
- Execute use when you need to work with backup and recovery. This skill provides backup automation and disaster recovery with comprehensive guidance and automation. Trigger with phrases like "create backups", "automate backups", or "implement disaster recovery".
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash(tar:*), Bash(rsync:*), Bash(aws:s3:*)
- compatibility
- Designed for Claude Code
- version
- 1.25.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- devops, backup, disaster-recovery
Planning Disaster Recovery
Overview
Design disaster recovery (DR) plans for cloud infrastructure covering RTO/RPO requirements, multi-region failover, data replication, and automated recovery procedures. Generate runbooks, Terraform for standby infrastructure, and automated failover scripts for databases, compute, and networking.
Prerequisites
- Complete inventory of production infrastructure components and dependencies
- Defined RTO (Recovery Time Objective) and RPO (Recovery Point Objective) per service tier
- Cloud provider CLI authenticated with permissions for multi-region resource management
- Cross-region networking configured (VPC peering, Transit Gateway, or VPN)
- Backup and replication mechanisms already in place or planned
Instructions
- Catalog all production services with their criticality tier (Tier 1: < 15 min RTO, Tier 2: < 1 hour, Tier 3: < 24 hours)
- Map dependencies between services to identify single points of failure and cascading failure paths
- Design the DR strategy per tier: active-active for Tier 1, pilot light or warm standby for Tier 2, backup-restore for Tier 3
- Generate Terraform for standby region infrastructure: VPC, subnets, security groups, and scaled-down compute
- Configure database replication: RDS cross-region read replicas, DynamoDB global tables, or Cloud SQL cross-region replicas
- Set up DNS failover using Route 53 health checks, Cloud DNS routing policies, or global load balancers
- Create automated failover scripts: promote read replica to primary, update DNS records, scale up standby compute
- Document the DR runbook with step-by-step procedures, responsible parties, and communication plans
- Schedule quarterly DR drills: simulate region failure, execute the runbook, measure actual RTO/RPO, and document gaps
- Set up monitoring for replication lag, backup freshness, and standby infrastructure health
Output
- DR plan document with service tiers, RTO/RPO targets, and recovery procedures
- Terraform modules for standby region infrastructure
- Automated failover scripts (database promotion, DNS switching, compute scaling)
- DR drill checklist and post-drill assessment template
- Monitoring dashboards for replication lag and backup status
Show full SKILL.md (210 more words)Show less
Error Handling
| Error | Cause | Solution |
|---|---|---|
Replication lag exceeds RPO | Network throughput insufficient or write volume too high | Increase replication instance size, enable compression, or implement write throttling during peak |
DNS failover not triggering | Health check misconfigured or TTL too high | Verify health check endpoint returns proper status; reduce DNS TTL to 60 seconds before drill |
Standby database promotion failed | Replication broken or standby in inconsistent state | Check replication status; if broken, restore from latest snapshot and re-establish replication |
Insufficient capacity in DR region | Instance types unavailable in standby region | Pre-provision reserved capacity in DR region or use multiple instance type options |
Application cannot connect after failover | Connection strings hardcoded to primary region endpoints | Use DNS-based endpoints (CNAME/Route 53) instead of direct IPs; parameterize region in config |
Examples
- "Create a disaster recovery plan for a 3-tier web application on AWS with < 15 minute RTO for the API layer and < 1 hour for batch processing."
- "Generate Terraform for a warm standby in us-west-2 with RDS cross-region read replica, scaled-down ECS cluster, and Route 53 failover routing."
- "Design a DR drill that simulates primary region failure, executes automated failover, and validates data integrity in the standby region."
Resources
- AWS Disaster Recovery: https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/
- GCP DR planning: https://cloud.google.com/architecture/dr-scenarios-planning-guide
- Azure Business Continuity: https://learn.microsoft.com/en-us/azure/reliability/
- DR strategy patterns:
© 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 3 other files (scripts, references, assets) in skills/.curated/planning-disaster-recovery of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- assets/README.md
- references/README.md
- scripts/README.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Planning Disaster Recovery 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Planning Disaster Recovery this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| OmniRoute Backup and Sync CLIdiegosouzapw/OmniRoute | 75k | — | ~948 | Automated safety check: Pass | MIT | |
| Pymobiledevice3 Device Operatordoronz88/pymobiledevice3 | 2.9k | — | ~1.8k | Automated safety check: Notes | GPL-3.0 | |
| Myclaw BackupLeoYeAI/openclaw-backup | 659 | — | ~1.8k | Automated safety check: Pass | MIT | |
| OmniRoute Database Backupsdiegosouzapw/OmniRoute | 75k | — | ~395 | Automated safety check: Pass | MIT | |
| Tempsgotempsh/temps | 833 | — | ~2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Pymobiledevice3 Device Operator
doronz88/pymobiledevice3
Operate iOS and iPadOS devices with pymobiledevice3, from a local checkout or straight from PyPI via uvx on a fresh workstation.
Myclaw Backup
LeoYeAI/openclaw-backup
Backup and restore all OpenClaw configuration, agent memory, skills, and workspace data.
OmniRoute Database Backups
diegosouzapw/OmniRoute
Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.
Temps
gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
Hermes Offsite Backup
OnlyTerp/hermes-optimization-guide
Set up encrypted off-machine Hermes backups. An agent skill from OnlyTerp/hermes-optimization-guide.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming 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.
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.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
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.
Related
Categories
Questions about Planning Disaster Recovery
What does Planning Disaster Recovery do?
Execute use when you need to work with backup and recovery. An agent skill from jeremylongshore/tons-of-skills-marketplace. Planning Disaster Recovery is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute use when you need to work with backup and recovery.
When should I use Planning Disaster Recovery?
Planning Disaster Recovery fits situations like: you need to work with backup and recovery; with phrases like create backups; automate backups; implement disaster recovery.
How do I install Planning Disaster Recovery in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a claude-code`. Or copy the skill folder (skills/.curated/planning-disaster-recovery in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/planning-disaster-recovery in your project. Claude Code loads it when a task matches its description.
How do I install Planning Disaster Recovery in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill planning-disaster-recovery -a codex`. Or copy the skill folder (skills/.curated/planning-disaster-recovery in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/planning-disaster-recovery in your project. Codex loads it when a task matches its description.
Can I use Planning Disaster Recovery 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 planning-disaster-recovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-disaster-recovery, .gemini/skills/planning-disaster-recovery, .github/skills/planning-disaster-recovery and .opencode/skills/planning-disaster-recovery in your project.
What does Planning Disaster Recovery need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning Disaster Recovery is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(tar:*), Bash(rsync:*), Bash(aws:s3:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Planning Disaster Recovery access the network?
SKILL.md names 3 domains. As links in the text: docs.aws.amazon.com, cloud.google.com and learn.microsoft.com. This is read from the text; nothing was executed.
Is Planning Disaster Recovery 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 Planning Disaster Recovery use?
Planning Disaster Recovery 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 Planning Disaster Recovery use?
About 1.2k tokens (SKILL.md is roughly 4.6k 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 17 tokens, read only when the agent opens those files.
What are the alternatives to Planning Disaster Recovery?
Skills that share tags, products or a category with Planning Disaster Recovery: OmniRoute Backup and Sync CLI (diegosouzapw/OmniRoute, 75k stars), Pymobiledevice3 Device Operator (doronz88/pymobiledevice3, 2.9k stars), Myclaw Backup (LeoYeAI/openclaw-backup, 659 stars) and OmniRoute Database Backups (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planning Disaster Recovery?
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.