find-skills
Use when the user wants to discover, evaluate, and install an existing agent skill or reusable workflow for a specific task or domain.
- License 许可
- MIT
- 所属仓库
- zyadgfh/Z-Syst
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- find-skills
- description
- Use when the user wants to discover, evaluate, and install an existing agent skill or reusable workflow for a specific task or domain.
- argument-hint
- [task or domain]
03 SKILL.md 正文
Find Skills
Use this skill when the user wants help with a task that may already exist as a reusable skill, workflow, or capability.
When to Use
Use this skill when the user:
- asks "how do I do X?"
- asks "find a skill for X"
- asks "is there a skill that can..."
- wants to extend agent capabilities
- mentions a domain such as design, testing, deployment, documentation, review, or automation
Skip this skill for tasks that are clearly one-off, highly specific, or already well understood without needing a reusable skill.
Workflow
1. Understand the need
- Identify the domain and the specific task.
- Clarify the user’s goal, expected outcome, and constraints.
- Decide whether the request is common enough that an existing skill is likely.
2. Check trusted sources first
- Prefer well-known and reputable skill sources.
- Look for widely used options from established maintainers or official ecosystems.
- Favor skills with clear documentation, recent maintenance, and a strong fit to the request.
3. Search for candidates
- Search skill directories or skill-based tooling when available.
- Try relevant keywords and alternate terms.
- If needed, search broader concepts such as "review", "deployment", "design", or "testing".
4. Evaluate before recommending
- Prefer skills that are relevant, documented, and credible.
- Avoid recommending low-quality, obscure, or poorly maintained options.
- If a match is weak, explain the tradeoff instead of forcing a recommendation.
5. Present the best options clearly
When you find a relevant skill, include:
- the skill name
- what it does
- why it fits the request
- source or reputation notes
- installation or usage guidance if available
6. Offer the next step
- If the user wants, install or configure the skill.
- If no suitable skill exists, say so directly and offer to help manually.
- If the workflow is recurring, suggest creating a custom skill.
Quality Criteria
A good recommendation should:
- match the user’s real need
- come from a trustworthy and relevant source
- be easy to understand and use
- avoid overclaiming when no strong match exists
Example Prompts
- "Find a skill for PR reviews."
- "Is there a skill to help me create a changelog?"
- "Help me discover a skill for frontend design patterns."
- "I need a workflow for deployment automation."
Example Response Pattern
Use this structure when presenting a match:
- Briefly acknowledge the request.
- Name the most relevant skill.
- Explain why it fits.
- Share installation or usage steps if available.
- Offer to help refine the search or install it.
When No Skill Is Found
If nothing suitable is found:
- say that clearly
- offer to help with the task directly
- suggest creating a custom skill if the workflow should be reusable
04 同仓库更多 Skills
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).
supabase-postgres-best-practices
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
code-vulnscan
Use this when the user wants to find security vulnerabilities in a codebase, perform a security audit, scan for CVEs, detect secrets, review React/Next.js or Go services, audit architecture/application/infrastructure flaws, review auth/API/crypto/business logic, check IaC/cloud/runtime configs, or generate a vulnerability report. Performs taint-flow, control-flow, architecture, and exploitability analysis across Python, JS/TS, Java, Go, PHP, Ruby, C/C++, C#, Rust, and infrastructure.
z-syst-pharmacy
Z-Syst Pharmacy Management System - Comprehensive rules for building a professional pharmacy management system using Laravel. Covers products, stock, purchases, sales, invoices, prescriptions, finance, reports, and SaaS expansion. Follow strict engineering principles: clean architecture, service layer pattern, database-first design, and audit-trail tracking.
ui-ux-promax
Brief description of what this Skill does and when to use it