framework_eng/skills/other/find-skills/SKILL.md
Use for discovering and installing agent skills when the user asks whether there is a skill for X or wants to extend capabilities. Helps find a suitable skill through `npx skills find` and install it.
npx skillsauth add steelmorgan/1c-agent-based-dev-framework 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.
Discover and install skills from the open agent skills ecosystem (npx skills).
User asks "how do I do X", "find a skill for X", "can you do X", wants to extend capabilities, or mentions a specific domain (design, testing, deployment, etc.).
npx skills find [query] # Search by keyword
npx skills add <owner/repo@skill> -g -y # Install globally
npx skills check # Check for updates
npx skills update # Update all
npx skills find <relevant keywords> (use specific terms: "react testing" > "testing")npx skills add <owner/repo@skill> -g -yIf no skills found: offer to help directly, suggest npx skills init for custom skill.
| 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 |
Machine-readable copy: domains.json next to this skill.
testing
MUST use BEFORE making a judgment about the cause of a conflict, a test failure, or an artifact dispute. Defines the end-to-end verification method L1→L6 and the classification of the first broken link.
development
MUST use AFTER a work cycle with ≥2 iterations (wrote → error → fixed → success). Provides the retrospective procedure and the format for recording practice/anti-patterns in references/learned-patterns.md or {project}/.context/learned-patterns.md.
tools
MUST use WHEN you are writing reusable knowledge into RLM (pattern / architectural decision / stable domain fact) OR reading it before a non-trivial task/solution in the domain. Provides the breakdown of native-push vs RLM-pull, tools for writing and reading RLM, H-MEM levels, and hygiene.
testing
MUST use WHEN the task is classified as simple (< 20 lines, 1 file, no new metadata objects, no architectural decisions). Provides a short cycle of 3 steps with a guard on the self path and mandatory verify.