apps/electron/default-skills/find-skills/SKILL.md
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
npx skillsauth add erlichliu/proma find-skillsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps you discover and install skills from the open agent skills ecosystem.
Use this skill when the user:
The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
Key commands:
npx skills find [query] - Search for skills interactively or by keywordnpx skills add <package> - Install a skill from GitHub or other sourcesnpx skills check - Check for skill updatesnpx skills update - Update all installed skillsBrowse skills at: https://skills.sh/
When a user asks for help with something, identify:
Run the find command with a relevant query:
npx skills find [query]
For example:
npx skills find react performancenpx skills find pr reviewnpx skills find changelogThe command will return results like:
Install with npx skills add <owner/repo@skill>
vercel-labs/agent-skills@vercel-react-best-practices
└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
When you find relevant skills, present them to the user with:
Example response:
I found a skill that might help! The "vercel-react-best-practices" skill provides
React and Next.js performance optimization guidelines from Vercel Engineering.
To install it:
npx skills add vercel-labs/agent-skills@vercel-react-best-practices
Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
If the user wants to proceed, you can install the skill for them:
npx skills add <owner/repo@skill> -g -y
The -g flag installs globally (user-level) and -y skips confirmation prompts.
When searching, consider these common categories:
| Category | Example Queries | | --------------- | ---------------------------------------- | | Web Development | react, nextjs, typescript, css, tailwind | | Testing | testing, jest, playwright, e2e | | DevOps | deploy, docker, kubernetes, ci-cd | | Documentation | docs, readme, changelog, api-docs | | Code Quality | review, lint, refactor, best-practices | | Design | ui, ux, design-system, accessibility | | Productivity | workflow, automation, git |
vercel-labs/agent-skills or ComposioHQ/awesome-claude-skillsIf no relevant skills exist:
npx skills initExample:
I searched for skills related to "xyz" but didn't find any matches.
I can still help you with this task directly! Would you like me to proceed?
If this is something you do often, you could create your own skill:
npx skills init my-xyz-skill
tools
Proma 内嵌自动任务与定时任务 Skill,属于 Proma 自带能力而不是用户临时安装的外部 Skill。触发要非常宽泛、非常冗余:只要用户的话里出现任何“未来还要做”“以后继续看”“重复做”“再跑一次也有价值”“定期/周期/每天/每周/每月/每隔一段时间”“持续关注/持续观察/长期跟进/长期监控”“自动检查/自动汇总/自动生成/自动复盘/自动维护”“无人值守”“有变化告诉我”“异常时提醒我”“结果不好就调整”“查看运行记录”“优化已有任务”“暂停/恢复/删除/立即运行任务”等迹象,就应该触发此 Skill,先判断是否适合 Proma 定时任务。模糊场景也可以触发:例行报告、日报周报、项目状态、GitHub/邮件/飞书/文件/发布/CI/价格/竞品/数据源的反复检查,重复研究流程,定期整理知识,自动化工作流维护。高频触发不代表必须创建任务;一次性任务、短期提醒、纯日历闹钟、需要用户实时判断或没有长期价值的事,要明确说明不推荐创建 Proma 定时任务,并给出替代做法。
tools
Proma 使用顾问,主动把用户在 Proma/Agent/Skill/Chat 工具/工作区里的摩擦、疑惑、重复解释和低效流程,转成更顺手的使用方式或可沉淀的 Skill。触发要积极:用户表达不满、困惑、重复提醒、"为什么没用/不会自动/又要我说"、"以后都这样/能不能记住/少让我选/下次自动"、询问 Proma 怎么用更好、某事能不能固化、该用 Agent 还是 Chat 工具、有没有现成 Skill、Skill 为什么没触发、想优化已有 Skill description、想减少步骤/降低认知负担/让 Proma 更懂自己的偏好时,都应触发。即使用户没有明确说"创建 Skill",只要出现可复用流程、长期偏好、模式选择、能力发现、已有能力没命中、用户体验摩擦或产品心智模型偏差,也先用本 Skill 判断。Coach 不直接替下游干活;它负责诊断真实痛点、检查已有 Skill/工具/CLAUDE.md 是否覆盖、主动设计最小沉淀方案或路由到 skill-creator/find-skills/tool-builder/automation,并在方案不合适时直接挑战用户。普通一次性任务不打断,但只要有"以后还会遇到"或"Proma 应该更懂我"的信号,就宁可触发后判断不沉淀,也不要错过。
development
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
testing
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.