Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
A business-oriented library that combines specialist instructions with practical tools and templates. Its examples start from the decision a deliverable needs to support, such as what a board meeting should resolve.
WHO IT'S FOR
Founders / Early-stage CEOs
generating jurisdiction-aware contracts and proposals
Product Managers / Growth Leads
designing SaaS churn reduction frameworks
Product Marketing Managers
conducting systematic competitor teardowns and SEO pages
Revenue Operations / Deal Desk
modeling channel economics and commercial policies
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Installs: A local checkout of the complete Claude Skills library: all 403 skills, 973 tools, and 76 agents. This procedure provides the files; it does not document automatic agent configuration.
Before you start
Git
Run from: Start in the directory where you want the checkout; the commands then enter Claude-Skills.
Run these commands in a terminal to clone the full repository and enter its root directory.
git clone https://github.com/borghei/Claude-Skills.git
cd Claude-Skills
Provide the PostgreSQL schema SQL file or paste its contents.
For a sample-based first run, use the skill's bundled assets/sample_schema.sql instead of your own schema.
Python 3 is needed if using the documented analysis script; run it from engineering/senior-backend/.
Use the senior-backend skill to analyze my PostgreSQL schema for missing indexes and N+1 risks. Summarize the most useful fixes and explain their rationale. Keep this first pass to analysis without generating or applying migrations.
Provide an LCOV, Istanbul JSON, or Cobertura XML coverage report.
Provide the test framework and language, plus relevant source code for meaningful test suggestions.
The bundled assets/sample_coverage_gaps.lcov is an optional sample input.
Python is needed if using the documented scripts/tdd.py coverage command.
Use the tdd-guide skill to analyze my coverage report against an 80% threshold. Identify the three highest-priority coverage gaps, include uncovered lines where available, and suggest the first test case to write for each.
Specify Apple App Store or Google Play and the target market or locale.
Provide the app category, current title and subtitle or short description, and seed keywords.
Specify whether the primary goal is ranking visibility or conversion.
Load the skill's matching metadata workflow and platform-requirements references when performing the review.
Use the app-store-optimization skill to review the app listing metadata I provide. Suggest an improved title and subtitle or short description for my platform and locale, check their character limits, and explain the keyword placement choices. Use my supplied data and keep the result to draft recommendations.