Sign InOpen Brain
GitHubGitHub RepoNeeds Review

tech-leads-club/agent-skills

A cross-agent skill registry adds scanning, integrity checks, and auditable installs for teams that want reusable coding-agent workflows without blindly trusting marketplace packages.

GitHub · Trending today
Open Source Open MarkdownOpen JSON
Source Summary

Agent Skills packages workflows for Cursor, Claude Code, Copilot, and other agents behind a CLI and MCP server. The repository says marketplace research found **13.4%** of skills had critical issues; its catalog is **100% open source**, contains no binaries, and is scanned before publishing.

Practical Implication

Treat agent skills as executable supply-chain inputs. Pin them through lockfiles and **content hashing**, prefer project-local copies when appropriate, inspect prompts and references, and use the audit log when updating or removing installed capabilities.

Agent-Ready Context
Agent Skills packages workflows for Cursor, Claude Code, Copilot, and other agents behind a CLI and MCP server. The repository says marketplace research found **13.4%** of skills had critical issues; its catalog is **100% open source**, contains no binaries, and is scanned before publishing.

Treat agent skills as executable supply-chain inputs. Pin them through lockfiles and **content hashing**, prefer project-local copies when appropriate, inspect prompts and references, and use the audit log when updating or removing installed capabilities.

The security posture is described by the maintainers, and the marketplace comparison is not substantiated in the supplied material. Human curation and **Snyk Agent Scan** reduce known risks but do not prove that a skill's instructions are safe or suitable for your repository.
Connected Context · Feed7 Judgment

Agent Skills turns portable skill installation into an explicit dependency-management and supply-chain problem. Compared with broader calls for skill governance, it adds concrete controls—source-only artifacts, scanning, lockfiles, content hashes, local copies, and update logs—while narrowing their assurance: maintainer curation and scanners reduce known exposure but cannot establish instruction safety or repository fit.

We Vetted 2000 AI Skills Before They Reached Developers — Lucas Palma, NubankNubank independently reinforces the need to scan and review skills before distribution, while showing that deterministic and LLM checks still need governance and measured effectiveness.We let an AI agent execute Bash and lived to talk about it — Sarah Sanders, PostHogPostHog broadens the same supply-chain model from installed skills to every context source and supports reserving blocking decisions for deterministic controls.affaan-m/ECCECC demonstrates how large skill and harness catalogs magnify configuration, audit, and upgrade risk, supporting Agent Skills’s pinning and selective-installation practices.SafeEvolve: Harness-Policy Co-Evolution from Agent Experience for Safety AlignmentSafeEvolve complements static pinning by proposing reversible skill and harness updates derived from trajectories, making provenance and rollback important when capabilities evolve.
Context Map
agentcodingsecurity#skills#harness-engineering#agent-reliability
Uncertainty
The security posture is described by the maintainers, and the marketplace comparison is not substantiated in the supplied material. Human curation and **Snyk Agent Scan** reduce known risks but do not prove that a skill's instructions are safe or suitable for your repository.