项目优化分析

本条目介绍 项目优化分析 的公开用途。DeepSkill 当前公开目录说明:“分析当前项目在代码质量、功能差距、文档、安全性、竞争格局和变现机会方面的状况,然后提交优先级排序的 GitHub 问题。当用户说“改进这个”、“分析这个项目”、“寻找改进点”或“填充待办事项”时使用。” 适用场景包括写代码与代码审查、测试与安全校验。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "improve":https://skillpi.com/zh/skills/deepskill-4766a9e4fa8b9b0263718c8bacdc18944e9c0907519bcda397e44067b665674a。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/productivity/claude-workflow-skills/skills/improve/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/productivity/claude-workflow-skills/skills/improve --skill improve
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目介绍 项目优化分析 的公开用途。DeepSkill 当前公开目录说明:“分析当前项目在代码质量、功能差距、文档、安全性、竞争格局和变现机会方面的状况,然后提交优先级排序的 GitHub 问题。当用户说“改进这个”、“分析这个项目”、“寻找改进点”或“填充待办事项”时使用。” 适用场景包括写代码与代码审查、测试与安全校验。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
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`.

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

| # | Title | Label | Priority |
|---|-------|-------|----------|
| 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)

当前收录版本

0.0.1

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值85/100
评分依据

提供项目多维度分析能力,覆盖代码质量、功能差距、文档、安全性、竞争格局和变现机会

触发精准85/100
评分依据

触发词覆盖合理,能准确匹配用户使用场景

结构规范90/100
评分依据

结构完整,包含 Step 0-9 的完整流程

执行可靠85/100
评分依据

工具来源明确,使用 gh CLI 工具

证据可验 (前四项均值)86/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

  • 账号、密钥或授权

    使用专用、最小权限账号,不把密钥粘贴到公开内容或命令日志;核对接收数据的服务与租户。

    主文档提及 · 第 85 行

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。