Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Full pipeline for CI/CD pipeline design, build, monitoring, and optimization.
Install Cicd Pipeline
$ npx skills add revfactory/harness-100 --skill cicd-pipeline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 cicd-pipeline --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/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/cicd-pipeline .claude/skills/cicd-pipeline && 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 "cicd-pipeline" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/cicd-pipeline into .claude/skills/cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cicd-pipeline", 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/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/cicd-pipelineType 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 revfactory/harness-100 --skill cicd-pipeline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 cicd-pipeline --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/cicd-pipeline .agents/skills/cicd-pipeline && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cicd-pipeline" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/cicd-pipeline into .agents/skills/cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cicd-pipeline", 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 revfactory/harness-100 --skill cicd-pipeline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 cicd-pipeline --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/cicd-pipeline .cursor/skills/cicd-pipeline && 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 "cicd-pipeline" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/cicd-pipeline into .cursor/skills/cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cicd-pipeline", 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/revfactory/harness-100.git --path en/20-cicd-pipeline/.claude/skills/cicd-pipeline--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 revfactory/harness-100 --skill cicd-pipeline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 cicd-pipeline --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/cicd-pipeline .gemini/skills/cicd-pipeline && 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 "cicd-pipeline" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/cicd-pipeline into .gemini/skills/cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cicd-pipeline", 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 revfactory/harness-100 cicd-pipelineInstalls 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 revfactory/harness-100 --skill cicd-pipeline -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/cicd-pipeline .github/skills/cicd-pipeline && 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 "cicd-pipeline" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/cicd-pipeline into .github/skills/cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cicd-pipeline", 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 revfactory/harness-100 --skill cicd-pipeline -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 cicd-pipeline --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/20-cicd-pipeline/.claude/skills/cicd-pipeline .opencode/skills/cicd-pipeline && 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 "cicd-pipeline" agent skill from https://github.com/revfactory/harness-100/tree/main/en/20-cicd-pipeline/.claude/skills/cicd-pipeline into .opencode/skills/cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cicd-pipeline", 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
cicd-pipeline- GitHub stars
- 1.3k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 680 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Full pipeline for CI/CD pipeline design, build, monitoring, and optimization.
- Works in 3 steps: Preparation (Performed directly by the… → Team Assembly and Execution → Integration and Final Artifacts
- Any CI/CD task including create a CI/CD pipeline
- SKILL.md covers Execution Mode, Agent Composition, Workflow and Mode by Task Scale, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cicd Pipeline is an agent skill from revfactory/harness-100. Full pipeline for CI/CD pipeline design, build, monitoring, and optimization. An agent team collaborates to perform stage design, YAML configuration generation, security scan integration, and monitoring/alert design. Use this skill for any CI/CD task including 'create a CI/CD pipeline', 'GitHub Actions', 'GitLab CI', 'Jenkins pipeline', 'deployment automation', 'build pipeline', 'DevOps pipeline', 'auto deploy', 'CI setup', 'CD setup', etc. Also supports optimization and security hardening for existing pipelines…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering CI/CD and Security review. It works with Amazon Web Services, Google Cloud, GitHub Actions and GitLab. The licence is Apache-2.0.
When your agent uses it
- Any CI/CD task including create a CI/CD pipeline
- Jenkins pipeline
- Deployment automation
- DevOps pipeline
Example prompts
- “create a CI/CD pipeline”
- “GitHub Actions”
- “GitLab CI”
- “/cicd-pipeline”
Requirements
- Python 3
- Node.js
- Docker
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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
Cicd Pipeline loads about 1.8k tokens when it runs. Until then it costs about 171 tokens; SKILL.md has 680 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 680 words, ~1,822 tokens.
Download SKILL.mdSave it as
.claude/skills/cicd-pipeline/SKILL.md (or your agent's skills folder).- name
- cicd-pipeline
- description
- Full pipeline for CI/CD pipeline design, build, monitoring, and optimization. An agent team collaborates to perform stage design, YAML configuration generation, security scan integration, and monitoring/alert design. Use this skill for any CI/CD task including 'create a CI/CD pipeline', 'GitHub Actions', 'GitLab CI', 'Jenkins pipeline', 'deployment automation', 'build pipeline', 'DevOps pipeline', 'auto deploy', 'CI setup', 'CD setup', etc. Also supports optimization and security hardening for existing pipelines. Note: actual infrastructure provisioning (AWS/GCP resource creation), server configuration, and cluster management are outside the scope of this skill.
CI/CD Pipeline — Pipeline Design, Build, Monitoring, and Optimization
An agent team collaborates to perform CI/CD pipeline design, configuration generation, security integration, and monitoring in a single pass.
Execution Mode
Agent Team — 5 members communicate directly via SendMessage and cross-validate each other's work.
Agent Composition
| Agent | File | Role | Type |
|---|---|---|---|
| pipeline-designer | .claude/agents/pipeline-designer.md | Stage design, branch strategy, deployment strategy | general-purpose |
| infra-engineer | .claude/agents/infra-engineer.md | Runners, containers, secrets, environment configuration | general-purpose |
| monitoring-specialist | .claude/agents/monitoring-specialist.md | Metrics, alerts, dashboards, DORA | general-purpose |
| security-scanner | .claude/agents/security-scanner.md | SAST, SCA, container scanning, secret detection | general-purpose |
| pipeline-reviewer | .claude/agents/pipeline-reviewer.md | Efficiency, reliability, security, alignment verification | general-purpose |
Workflow
Phase 1: Preparation (Performed directly by the orchestrator)
- Extract from user input:
- Project Type: Language/framework (Node.js, Python, Go, Java, etc.)
- CI/CD Tool: GitHub Actions / GitLab CI / Jenkins
- Deployment Target: AWS / GCP / Azure / Kubernetes / Docker
- Branch Strategy (optional): GitFlow, Trunk-based
- Existing Files (optional): Existing CI/CD configuration, Dockerfile, etc.
- Create the
_workspace/directory at the project root - Organize the input and save to
_workspace/00_input.md - If existing files are provided, copy them to
_workspace/and skip the corresponding phase - Determine the execution mode based on the scope of the request
Phase 2: Team Assembly and Execution
| Order | Task | Owner | Dependencies | Artifact |
|---|---|---|---|---|
| 1 | Pipeline Design | pipeline-designer | None | _workspace/01_pipeline_design.md |
| 2a | Infrastructure Config | infra-engineer | Task 1 | _workspace/02_pipeline_config/, 02_infra_config.md |
| 2b | Security Scan Design | security-scanner | Task 1 | _workspace/04_security_scan.md |
| 3 | Monitoring Design | monitoring-specialist | Tasks 1, 2a | _workspace/03_monitoring.md |
| 4 | Pipeline Review | pipeline-reviewer | Tasks 2a, 2b, 3 | _workspace/05_review_report.md |
Tasks 2a (infrastructure) and 2b (security) are executed in parallel.
Inter-team communication flow:
- pipeline-designer completes -> Delivers stage requirements to infra-engineer, scan placement to security-scanner, deployment strategy to monitoring-specialist
- infra-engineer completes -> Delivers log/metric points to monitoring-specialist, image/dependency paths to security-scanner
- security-scanner completes -> Delivers security alert rules to monitoring-specialist
- pipeline-reviewer cross-validates all artifacts. When 🔴 must-fix issues are found, requests revisions from the relevant agent -> rework -> re-verify (up to 2 rounds)
Phase 3: Integration and Final Artifacts
Organize the final artifacts based on the review report:
- Verify all files in
_workspace/ - Confirm that all 🔴 must-fix items from the review report have been addressed
- Report the final summary to the user
Mode by Task Scale
| User Request Pattern | Execution Mode | Agents Deployed |
|---|---|---|
| "Create a CI/CD pipeline", "full design" | Full Pipeline | All 5 agents |
| "Just set up CI" | CI Mode | pipeline-designer + infra-engineer + pipeline-reviewer |
| "Add security scanning to this pipeline" (existing config) | Security Mode | security-scanner + pipeline-reviewer |
| "Design pipeline monitoring" (existing config) | Monitoring Mode | monitoring-specialist + pipeline-reviewer |
| "Review this CI/CD config" | Review Mode | pipeline-reviewer only |
Leveraging existing files: If the user provides YAML, Dockerfile, or other existing files, skip the corresponding steps.
Show full SKILL.md (261 more words)Show less
Data Transfer Protocol
| Strategy | Method | Purpose |
|---|---|---|
| File-based | _workspace/ directory | Store and share primary artifacts |
| Message-based | SendMessage | Real-time delivery of key information, revision requests |
| Task-based | TaskCreate/TaskUpdate | Progress tracking, dependency management |
File naming convention: {order}_{agent}_{artifact}.{extension}
Error Handling
| Error Type | Strategy |
|---|---|
| CI/CD tool not specified | Default to GitHub Actions |
| Deployment target not specified | Docker container-based generic configuration |
| Agent failure | Retry once -> If still fails, proceed without that artifact; note the omission in the review report |
| 🔴 found during review | Request revision from the relevant agent -> rework -> re-verify (up to 2 rounds) |
| Existing YAML parsing failure | Manually analyze and create new configuration files |
Test Scenarios
Normal Flow
Prompt: "Create a GitHub Actions CI/CD pipeline for a Node.js Express app. I want to deploy to AWS ECS with a Canary deployment strategy" Expected Result:
- Design: CI (lint -> test -> build -> scan) + CD (staging -> approval -> canary -> rollout)
- Infrastructure: GitHub Actions YAML, Dockerfile, ECR config, secret management
- Security: Semgrep + Trivy + Gitleaks configuration
- Monitoring: DORA metrics, build/deploy alerts, dashboards
- Review: All items in the alignment matrix verified
Existing File Flow
Prompt: "Add security scanning to this GitHub Actions config" + YAML file Expected Result:
- Copy existing YAML to
_workspace/02_pipeline_config/ - Security mode: deploy security-scanner + pipeline-reviewer
- Skip pipeline-designer, infra-engineer, monitoring-specialist
Error Flow
Prompt: "Create a CI/CD quickly, Python project" Expected Result:
- Deployment target not specified -> Docker-based generic design
- GitHub Actions selected as default
- Review report notes "deployment target unspecified, Docker container-based generic configuration"
Agent Extension Skills
Extension skills that enhance each agent's domain expertise:
| Skill | Target Agent | Role |
|---|---|---|
pipeline-security-gates | security-scanner | SAST/SCA/secret detection tool selection, gate placement, thresholds |
deployment-strategies | pipeline-designer | Blue-Green/Canary/Rolling deployment, rollback, DORA metrics |
© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/20-cicd-pipeline/.claude/skills/cicd-pipeline of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Cicd Pipeline 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 |
|---|---|---|---|---|---|---|
| Cicd Pipeline this skillrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Tirith PoliciesStackGuardian/tirith | 170 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Playwright CIzebbern/claude-code-guide | 4.7k | 2 repos | ~675 | Automated safety check: Pass | MIT | |
| CI CDRightNow-AI/openfang | 18k | — | ~691 | Automated safety check: Pass | Apache-2.0 | |
| Building CI Pipelinesancoleman/ai-design-components | 526 | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
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…
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
Building CI Pipelines
ancoleman/ai-design-components
Constructs secure, efficient CI/CD pipelines with supply chain security (SLSA), monorepo optimization, caching strategies, and parallelization patterns for GitHub Actions, GitLab CI, and Argo…
Newman Cicd Integration
sickn33/agentic-awesome-skills
Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing.
More from revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Categories
Questions about Cicd Pipeline
What does Cicd Pipeline do?
Full pipeline for CI/CD pipeline design, build, monitoring, and optimization. Cicd Pipeline is an agent skill from revfactory/harness-100. Full pipeline for CI/CD pipeline design, build, monitoring, and optimization.
When should I use Cicd Pipeline?
Cicd Pipeline fits situations like: any CI/CD task including create a CI/CD pipeline; jenkins pipeline; deployment automation; devOps pipeline.
How do I install Cicd Pipeline in Claude Code?
Run `npx skills add revfactory/harness-100 --skill cicd-pipeline -a claude-code`. Or copy the skill folder (en/20-cicd-pipeline/.claude/skills/cicd-pipeline in revfactory/harness-100) into .claude/skills/cicd-pipeline in your project. Claude Code loads it when a task matches its description.
How do I install Cicd Pipeline in Codex?
Run `npx skills add revfactory/harness-100 --skill cicd-pipeline -a codex`. Or copy the skill folder (en/20-cicd-pipeline/.claude/skills/cicd-pipeline in revfactory/harness-100) into .agents/skills/cicd-pipeline in your project. Codex loads it when a task matches its description.
Can I use Cicd Pipeline 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 revfactory/harness-100 --skill cicd-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cicd-pipeline, .gemini/skills/cicd-pipeline, .github/skills/cicd-pipeline and .opencode/skills/cicd-pipeline in your project.
What does Cicd Pipeline need to run?
SKILL.md names no scripts, command-line tools or credentials: Cicd Pipeline is instructions for the agent only. Our summary lists: Python 3; Node.js; Docker.
Does Cicd Pipeline 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 Cicd Pipeline 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. Review the folder before installing.
What licence does Cicd Pipeline use?
Cicd Pipeline is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cicd Pipeline use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cicd Pipeline?
Skills that share tags, products or a category with Cicd Pipeline: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Tirith Policies (StackGuardian/tirith, 170 stars), Playwright CI (zebbern/claude-code-guide, 4.7k stars) and CI CD (RightNow-AI/openfang, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cicd Pipeline?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,295 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.