CI CD Patterns
softspark/ai-toolkit
CI/CD: GitHub Actions, GitLab CI, Jenkins, caching, blue-green, canary.
Execute use when you need to work with deployment and CI/CD.
Install Building Cicd Pipelines
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-cicd-pipelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-cicd-pipelines --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/building-cicd-pipelines .claude/skills/building-cicd-pipelines && 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 "building-cicd-pipelines" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-cicd-pipelines into .claude/skills/building-cicd-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-cicd-pipelines", 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/building-cicd-pipelinesType 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 building-cicd-pipelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-cicd-pipelines --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/building-cicd-pipelines .agents/skills/building-cicd-pipelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "building-cicd-pipelines" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-cicd-pipelines into .agents/skills/building-cicd-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-cicd-pipelines", 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 building-cicd-pipelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-cicd-pipelines --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/building-cicd-pipelines .cursor/skills/building-cicd-pipelines && 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 "building-cicd-pipelines" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-cicd-pipelines into .cursor/skills/building-cicd-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-cicd-pipelines", 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/building-cicd-pipelines--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 building-cicd-pipelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace building-cicd-pipelines --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/building-cicd-pipelines .gemini/skills/building-cicd-pipelines && 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 "building-cicd-pipelines" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-cicd-pipelines into .gemini/skills/building-cicd-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-cicd-pipelines", 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 building-cicd-pipelinesInstalls 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 building-cicd-pipelines -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/building-cicd-pipelines .github/skills/building-cicd-pipelines && 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 "building-cicd-pipelines" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-cicd-pipelines into .github/skills/building-cicd-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-cicd-pipelines", 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 building-cicd-pipelines -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 building-cicd-pipelines --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/building-cicd-pipelines .opencode/skills/building-cicd-pipelines && 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 "building-cicd-pipelines" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/building-cicd-pipelines into .opencode/skills/building-cicd-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "building-cicd-pipelines", 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
building-cicd-pipelines- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 454 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 deployment and CI/CD.
- Works in 10 steps: Scan the project for existing CI/CD… → Identify the application stack:… → Define pipeline stages: lint -> test ->… → …
- You need to work with deployment and CI/CD
- SKILL.md covers Current State, Overview, Prerequisites and Instructions, plus 4 more sections
- Calls npm, go and docker
What it does
Building Cicd Pipelines is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute use when you need to work with deployment and CI/CD. This skill provides deployment automation and pipeline orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
Its SKILL.md is about 1.1k 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 CI/CD and Deployment. It works with GitLab, GitHub Actions and Jenkins. 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 deployment and CI/CD
- With phrases like deploy application
- Create pipeline
- Automate deployment
Example prompts
- “deploy application”
- “create pipeline”
- “automate deployment”
- “/building-cicd-pipelines”
Requirements
- Python 3
- Node.js
- Docker
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(git:*), Bash(docker:*), Bash(kubectl:*)
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Scan the project for existing CI/CD configuration files (.github/workflows/, .gitlab-ci.yml, Jenkinsfile, .circleci/config.yml)
- Identify the application stack: language, framework, test runner, package manager, and deployment target
- Define pipeline stages: lint -> test -> build -> security-scan -> deploy-staging -> integration-test -> deploy-production
- Generate the pipeline configuration file with appropriate triggers (push to main, PR events, tags)
- Add caching for dependencies (node_modules, .pip-cache, Go modules) to reduce build times
- Configure matrix builds for multiple language versions or OS targets where appropriate
- Add secret references for deployment credentials, container registry tokens, and API keys (never hardcode)
- Implement deployment gates: manual approval for production, automated rollback on health check failure
- Add status badges and notifications (Slack, email) for build results
- Validate the pipeline syntax using platform-specific tools (actionlint, gitlab-ci-lint)
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(git:*)Bash(docker:*)Bash(kubectl:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
npmgodocker
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.github.comdocs.gitlab.comjenkins.iomartinfowler.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
Building Cicd Pipelines loads about 1.1k tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 454 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). 454 words, ~1,113 tokens.
Download SKILL.mdSave it as
.claude/skills/building-cicd-pipelines/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- building-cicd-pipelines
- description
- Execute use when you need to work with deployment and CI/CD. This skill provides deployment automation and pipeline orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash(git:*), Bash(docker:*), Bash(kubectl:*)
- compatibility
- Designed for Claude Code
- version
- 1.24.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- devops, deployment, ci-cd
Building CI/CD Pipelines
Current State
!ls .github/workflows/*.yml .gitlab-ci.yml Jenkinsfile .circleci/config.yml 2>/dev/null || echo 'No CI/CD config found'
Overview
Generate CI/CD pipeline configurations for GitHub Actions, GitLab CI, Jenkins, CircleCI, and Azure DevOps. Produce multi-stage workflows covering linting, testing, building container images, security scanning, and deploying to staging/production with proper gating and rollback mechanisms.
Prerequisites
- Git repository hosted on a supported platform (GitHub, GitLab, Bitbucket, Azure DevOps)
- Container runtime (Docker) if building images
- Target deployment environment credentials configured as pipeline secrets
- Test suite that can run headlessly (
npm test,pytest,go test, etc.) - Understanding of branching strategy (trunk-based, GitFlow, or environment branches)
Instructions
- Scan the project for existing CI/CD configuration files (
.github/workflows/,.gitlab-ci.yml,Jenkinsfile,.circleci/config.yml) - Identify the application stack: language, framework, test runner, package manager, and deployment target
- Define pipeline stages:
lint->test->build->security-scan->deploy-staging->integration-test->deploy-production - Generate the pipeline configuration file with appropriate triggers (push to main, PR events, tags)
- Add caching for dependencies (
node_modules,.pip-cache, Go modules) to reduce build times - Configure matrix builds for multiple language versions or OS targets where appropriate
- Add secret references for deployment credentials, container registry tokens, and API keys (never hardcode)
- Implement deployment gates: manual approval for production, automated rollback on health check failure
- Add status badges and notifications (Slack, email) for build results
- Validate the pipeline syntax using platform-specific tools (
actionlint,gitlab-ci-lint)
Output
- Pipeline configuration files (
.github/workflows/*.yml,.gitlab-ci.yml,Jenkinsfile) - Dockerfile for container builds (multi-stage, minimal base image)
- Deployment scripts or Kubernetes manifests referenced by the pipeline
- Environment-specific variable files for staging vs. production
Show full SKILL.md (193 more words)Show less
Error Handling
| Error | Cause | Solution |
|---|---|---|
Pipeline triggered but no jobs run | Trigger conditions (paths, branches) do not match | Review on: / only: / rules: filters and verify branch names |
Docker build failed: layer cache miss | Cache key changed or cache storage expired | Use content-based cache keys (hashFiles('**/package-lock.json')) and verify cache backend |
Secret not found | Secret name mismatch or not set in pipeline settings | Check secret names match exactly (case-sensitive) in repository/project settings |
Deploy failed: unauthorized | Expired or incorrect deployment credentials | Rotate credentials, update pipeline secrets, and verify IAM role/service account permissions |
Tests pass locally but fail in CI | Environment differences (OS, node version, timezone) | Pin runtime versions in pipeline config; use matrix to test across environments |
Examples
- "Create a GitHub Actions workflow for a Node.js app: lint with ESLint, test with Jest, build Docker image, push to ECR, deploy to EKS staging on PR merge."
- "Generate a GitLab CI pipeline with parallel test jobs, SAST scanning, and manual production deployment gate."
- "Build a Jenkins pipeline that runs Python tests in a Docker agent, publishes coverage to SonarQube, and deploys via Terraform."
Resources
- GitHub Actions: https://docs.github.com/en/actions
- GitLab CI/CD: https://docs.gitlab.com/ee/ci/
- Jenkins Pipeline: https://www.jenkins.io/doc/book/pipeline/
- CI/CD best practices: https://martinfowler.com/articles/continuousIntegration.html
© 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/building-cicd-pipelines 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
Building Cicd Pipelines 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 |
|---|---|---|---|---|---|---|
| Building Cicd Pipelines this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| CI CD Patternssoftspark/ai-toolkit | 179 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| CI CDEliasOulkadi/shokunin | 114 | — | ~3.4k | Automated safety check: Notes | MIT | |
| Tirith PoliciesStackGuardian/tirith | 170 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| CI/CD Pipeline Principlesirahardianto/awesome-agv | 156 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Playwright CIzebbern/claude-code-guide | 4.7k | 2 repos | ~675 | Automated safety check: Pass | MIT |
Similar skills
CI CD
EliasOulkadi/shokunin
Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…
Tirith Policies
StackGuardian/tirith
Write, validate, run and debug Tirith IaC governance policies, install Tirith, and add it to a CI pipeline (GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps, CircleCI or any…
CI/CD Pipeline Principles
irahardianto/awesome-agv
Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.
Playwright CI
zebbern/claude-code-guide
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
CI CD
RightNow-AI/openfang
CI/CD pipeline expert for GitHub Actions, GitLab CI, Jenkins, and deployment automation
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
Works with
Categories
Questions about Building Cicd Pipelines
What does Building Cicd Pipelines do?
Execute use when you need to work with deployment and CI/CD. Building Cicd Pipelines is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute use when you need to work with deployment and CI/CD.
When should I use Building Cicd Pipelines?
Building Cicd Pipelines fits situations like: you need to work with deployment and CI/CD; with phrases like deploy application; create pipeline; automate deployment.
How do I install Building Cicd Pipelines in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-cicd-pipelines -a claude-code`. Or copy the skill folder (skills/.curated/building-cicd-pipelines in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/building-cicd-pipelines in your project. Claude Code loads it when a task matches its description.
How do I install Building Cicd Pipelines in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill building-cicd-pipelines -a codex`. Or copy the skill folder (skills/.curated/building-cicd-pipelines in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/building-cicd-pipelines in your project. Codex loads it when a task matches its description.
Can I use Building Cicd Pipelines 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 building-cicd-pipelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/building-cicd-pipelines, .gemini/skills/building-cicd-pipelines, .github/skills/building-cicd-pipelines and .opencode/skills/building-cicd-pipelines in your project.
What does Building Cicd Pipelines need to run?
Going by SKILL.md and its folder, Building Cicd Pipelines needs the command-line tools its instructions call (npm, go and docker). Our summary lists: Python 3; Node.js; Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(git:*), Bash(docker:*), Bash(kubectl:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Building Cicd Pipelines access the network?
SKILL.md names 4 domains. As links in the text: docs.github.com, docs.gitlab.com, jenkins.io and martinfowler.com. This is read from the text; nothing was executed.
Is Building Cicd Pipelines 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 Building Cicd Pipelines use?
Building Cicd Pipelines 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 Building Cicd Pipelines use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Building Cicd Pipelines?
Skills that share tags, products or a category with Building Cicd Pipelines: CI CD Patterns (softspark/ai-toolkit, 179 stars), CI CD (EliasOulkadi/shokunin, 114 stars), Tirith Policies (StackGuardian/tirith, 170 stars) and CI/CD Pipeline Principles (irahardianto/awesome-agv, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Building Cicd Pipelines?
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.