Tech Leads Club Agent Skills
Agent Skills
A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup
- 7,111 ★ on the repository
- Last commit
Extended access
Why this level
- The CLI downloads and writes files into agent configs
- Some skills run deploys, Playwright and CI tasks
Install
- Works in
Manual install
npx @tech-leads-club/agent-skillsInteractive wizard. Non-interactive: agent-skills install -s tlc-spec-driven -a cursor claude-code.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI downloads and writes files into agent configs
- Some skills run deploys, Playwright and CI tasks
This is third-party code. Review the repository files before installing.
What it does
The repository combines a skill catalog, an install CLI and an MCP server. The catalog covers architecture and decomposition, cloud deploys, ADRs, RFCs and design docs, spec-driven development, frontend and accessibility, performance, security, go-to-market, and working with Nx, Playwright, Figma, Sentry and Jira. The interactive CLI lets you pick skills, agents, install method and scope, and handles updates, removal and an audit log. Skills go through static analysis and Snyk Agent Scan before publishing. The MCP server lets the agent search skills by intent and load only the files it needs.
Who it is for. For engineering teams that want a shared, vetted skill set across different agents.
Good fit when
- You want the same skills in Cursor, Claude Code and Windsurf at once
- You need spec-driven development with plans, tasks and memory across sessions
- You want the agent to find the right skill itself over MCP
Not a fit when
- You need one specific skill without an install manager
- You have no access to npm or the project's CDN
Example request
Plan the report export feature with tlc-spec-driven: specification, design, tasksLimitations
The CLI and MCP server download skills from the project's CDN and need Node.js 22+. Third-party skills keep their own licenses; the project's own skills are CC-BY-4.0. All content is in English.
How to disable. Remove skills with agent-skills remove -s <name>, delete the agent-skills MCP server from your config, and clear the cache with agent-skills cache --clear if needed.
FAQ
How is it different from open marketplaces?
Skills are hand-curated, statically analyzed and scanned with Snyk Agent Scan, and the CLI pins content hashes in a lockfile and keeps an audit log.
Which agents are supported?
Claude Code, Cline, Cursor, GitHub Copilot, Windsurf, Gemini CLI, Codex, Roo Code, OpenCode and about ten more.
Discussion
No questions or reviews yet.
Related
SkillsBuilder Skills
Skills for agents
A set of small skills from Builder.io for agent work habits: visual plans and diff recaps, docs-first checks, cross-agent review and clean status updates
Softaworks Agent Toolkit
Softaworks Agent Skills
A marketplace of skills, subagents and commands for coding agents: development, documentation, planning and workplace communication
The author's personal set: shared agent rules and dozens of skills for GitHub, the browser, macOS, messaging and releases, plus a sync script
Dimillian Skills
Skills
A set of 16 engineering skills for agents: Apple platform work, macOS packaging, React performance, code review and refactoring
Two skills for coding agents: wtf audits a project before shipping, better-codex keeps the agent disciplined while working on code
Skills from the Dart team: tests and mocks, analysis and dart fix, CLI apps, FFI, documentation and package conflict fixes for an AI agent
README in short
The README explains what skills are, how the registry is secured and which agents are supported. It shows featured skills, the install wizard and full CLI reference: install, update, remove, cache, audit. It describes the MCP server with four tools and a config snippet. Code is MIT, the project's own skills are CC-BY-4.0.
README badge
Original SKILL.md
--- name: component-common-domain-detection description: Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis). --- # Common Domain Component Detection This skill identifies common domain functionality that is duplicated across multiple components and suggests consolidation opportunities to reduce duplication and improve maintainability. ## How to Use ### Quick Start Request analysis of your codebase: - **"Find common domain functionality across components"** - **"Identify duplicate domain logic that should be consolidated"** - **"Detect shared classes used across multiple components"** - **"Analyze consolidation opportunities for common components"** ### Usage Examples **Example 1: Find Common Functionality** ``` User: "Find common domain functionality across components" The skill will: 1. Scan component namespaces for common patterns 2. Detect shared classes used across components 3. Identify duplicate domain logic 4. Analyze coupling impact of consolidation 5. Suggest consolidation opportunities ```