New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Improve

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Analyses the current project across code quality, feature gaps, documentation, security, competitive landscape, and monetisation opportunities, then files prioritised GitHub issues.

MITAuto-check: notesDevelopment

Install Improve

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill improve -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace improve --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/improve .claude/skills/improve && rm -rf skills-src

Use ~/.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/

Facts

Skill name
improve
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
569 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Analyses the current project across code quality, feature gaps, documentation, security, competitive landscape, and monetisation opportunities, then files prioritised GitHub issues.

  • Works in 10 steps: Pre-flight check → Understand the project → Code quality and bugs → …
  • The user says improve this
  • SKILL.md covers Step 0: Pre-flight check, Step 1: Understand the project, Step 2: Code quality and bugs and Step 3: Feature completeness, plus 6 more sections
  • Calls gh, git and bash

What it does

Improve is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyses the current project across code quality, feature gaps, documentation, security, competitive landscape, and monetisation opportunities, then files prioritised GitHub issues. Use when the user says improve this, analyse this project, find improvements, or fill the backlog.

Its SKILL.md is about 1.3k 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 Development, covering Code quality. It works with GitHub and Git. 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

  • The user says improve this
  • Analyse this project
  • Find improvements
  • Fill the backlog

Example prompts

  • “Use the improve skill to analyse the current project across code quality, feature gaps, documentation, security, competitive landscape, and…”
  • “/improve”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash, WebSearch, WebFetch

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Pre-flight check
  2. Understand the project
  3. Code quality and bugs
  4. Feature completeness
  5. Documentation
  6. Security
  7. Competitive landscape
  8. Monetisation and passive income opportunities
  9. File GitHub issues
  10. Summary report

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:

    • Read
    • Glob
    • Grep
    • Bash
    • WebSearch
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    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

Improve loads about 1.3k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 569 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash, WebSearch, WebFetch

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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 569 words, ~1,345 tokens.

Download SKILL.mdSave it as .claude/skills/improve/SKILL.md (or your agent's skills folder).
name
improve
description
Analyses the current project across code quality, feature gaps, documentation, security, competitive landscape, and monetisation opportunities, then files prioritised GitHub issues. Use when the user says improve this, analyse this project, find improvements, or fill the backlog.
allowed-tools
Read, Glob, Grep, Bash, WebSearch, WebFetch
disable-model-invocation
true

Improve

Project: !basename $(git rev-parse --show-toplevel 2>/dev/null) 2>/dev/null || basename $PWD Open issues: !gh issue list --state open --json number --jq 'length' 2>/dev/null || echo "unknown" Last tag: !git describe --tags --abbrev=0 2>/dev/null || echo "none" Recent commits: !git log --oneline -5 2>/dev/null || echo "none"

Analyses the current project from multiple angles — technical, strategic, and commercial — then files actionable GitHub issues for every finding.

Step 0: Pre-flight check

bash
gh auth status 2>&1 || { echo "ERROR: gh is not authenticated. Run: gh auth login"; exit 1; }

Step 1: Understand the project

Read these files to build context before analysing anything:

  • README.md — stated purpose, audience, and feature set
  • CLAUDE.md — current status, decisions, next steps
  • Any .claude-plugin/plugin.json or manifest files — metadata and versioning

Then inventory all files:

bash
find . -not -path './.git/*' -type f | sort

Read a representative sample of source files to understand the implementation. Note: what does this project do, who is it for, and what problem does it solve?

Step 2: Code quality and bugs

Review source files for:

  • Logic errors, edge cases, or fragile assumptions
  • Anti-patterns or code that will break under realistic conditions
  • Inconsistent behaviour between similar components
  • Missing error handling at system boundaries (user input, external APIs)
  • Unnecessary complexity or premature abstraction
  • Hardcoded values that should be configurable

For shell scripts, also check:

bash
bash -n <script.sh>   # syntax check each script

Label findings: bug for defects, enhancement for quality improvements.

Step 3: Feature completeness

Based on the project's stated purpose in README.md, identify:

  • Features described but not yet implemented
  • Obvious gaps a user of this tool would expect
  • Incomplete workflows (things that almost work end-to-end but don't)
  • Integration opportunities with tools this project already touches

Label findings: enhancement.

Step 4: Documentation

  • Is the README sufficient for a new user to get started without help?
  • Are there undocumented behaviours or options?
  • Are examples present and accurate?
  • Is CLAUDE.md current with the real project state?
  • Are there missing or misleading inline comments in complex code?

Label findings: documentation.

Step 5: Security

Review for:

  • Credentials, tokens, or secrets that could be exposed
  • Shell injection risks in any scripts that interpolate external input
  • Insecure defaults (world-readable files, unvalidated input passed to system calls)
  • Dependencies with known vulnerabilities (check if a lock file or manifest is present)
  • Over-permissioned tool or API scopes

Label findings: security.

Show full SKILL.md (222 more words)Show less

Step 6: Competitive landscape

Search for similar projects, tools, or plugins in the same space:

  • What do competing or complementary tools offer that this project doesn't?
  • Are there recent developments in the ecosystem (new APIs, new frameworks) this project could leverage?
  • What are users asking for in issues/discussions on similar projects?

Use WebSearch to research. Focus on actionable gaps, not general observations.

Label findings: enhancement or idea.

Step 7: Monetisation and passive income opportunities

Think about realistic ways this project could generate passive income or build leverage:

  • Sponsorship hooks (GitHub Sponsors, Open Collective)
  • A premium or hosted tier (what would justify a paid version?)
  • Consulting or training services this project could anchor
  • Marketplace or integration listings (e.g. plugin marketplaces, app directories)
  • Companion products (templates, courses, related tools)
  • Licensing opportunities

Be concrete — vague suggestions are not useful. If an opportunity is real, describe exactly what would need to be built or done.

Label findings: idea.

Step 8: File GitHub issues

For each distinct finding across all dimensions, create one GitHub issue:

bash
gh issue create \
  --title "<category>: <brief description>" \
  --body "$(cat <<'EOF'
## Summary

<one paragraph describing the finding>

## Why it matters

<impact on users, security, revenue, or maintainability>

## Suggested approach

<concrete steps to address this>

## References

<links to competitive examples, docs, or research — if applicable>
EOF
)" \
  --label "<bug|enhancement|documentation|security|idea>"

Avoid duplicate issues — check existing open issues first:

bash
gh issue list --state open --limit 100

Note each issue number as you create it.

Step 9: Summary report

Output a table of all issues filed:

#TitleLabelPriority
N......High/Med/Low

Then call out:

  • Top 3 issues to address first and why
  • Most surprising finding
  • Highest-leverage opportunity (best return for effort)

© 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

Just SKILL.md in plugins/productivity/claude-workflow-skills/skills/improve of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Improve 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.

Improve compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Improve this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: NotesMIT
Databricks CLI PR Checklistdatabricks/cli404—~1.5kAutomated safety check: PassCustom licence
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT

Similar skills

  • Databricks CLI PR Checklist

    databricks/cli

    Official

    Pre-PR checklist for the Databricks CLI repository: run the same format and lint checks as CI, scrub the diff, fill the PR template concisely and add a changelog entry.

    404 GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing 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.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • 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.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • 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.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Improve

What does Improve do?

Analyses the current project across code quality, feature gaps, documentation, security, competitive landscape, and monetisation opportunities, then files prioritised GitHub issues. Improve is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyses the current project across code quality, feature gaps, documentation, security, competitive landscape, and monetisation opportunities, then files prioritised GitHub issues.

When should I use Improve?

Improve fits situations like: the user says improve this; analyse this project; find improvements; fill the backlog.

How do I install Improve in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill improve -a claude-code`. Or copy the skill folder (plugins/productivity/claude-workflow-skills/skills/improve in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/improve in your project. Claude Code loads it when a task matches its description.

How do I install Improve in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill improve -a codex`. Or copy the skill folder (plugins/productivity/claude-workflow-skills/skills/improve in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/improve in your project. Codex loads it when a task matches its description.

Can I use Improve 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 improve -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/improve, .gemini/skills/improve, .github/skills/improve and .opencode/skills/improve in your project.

What does Improve need to run?

Going by SKILL.md and its folder, Improve needs the command-line tools its instructions call (gh, git and bash). Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash, WebSearch, WebFetch.

Does Improve access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Improve safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Improve use?

Improve is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Improve use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Improve?

Skills that share tags, products or a category with Improve: Databricks CLI PR Checklist (databricks/cli, 404 stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Improve?

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.