Manages the installation and discovery of AI skills from the PartMe marketplace.
118 skills available
Manages the installation and discovery of AI skills from the PartMe marketplace.
对任意 Agent Skill 做 TRACE 五维度评测(T/R/A/C/E),输出 Markdown/HTML 报告与雷达图;当用户要求“TRACE 评测/打分/生成 TRACE 报告/五维度评估”或需要改进建议时使用。
Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations.
The canonical knowledge base for designing Agent Skills. Contains distilled Agent Skills specifications (naming conventions, frontmatter rules, directory structure, progressive disclosure), official best practices, description optimization techniques, script safety guidelines, and evaluation frameworks (TRACE). Use when designing a new skill, reviewing an existing skill for compliance, needing to know what makes a good skill, wondering about frontmatter rules or naming conventions, or when the user mentions "设计技能", "创建技能", "技能规范", "技能命名规则", "SKILL.md 怎么写", "frontmatter 规范", "技能最佳实践", "技能目录结构", "渐进式披露", "Agent Skills 规范".
Guide for creating Standard Operating Procedures and SOPs and composite workflows by combining atomic Agent Skills. Use when users want to design, structure, or implement multi-step workflows that orchestrate multiple skills for complex business goals. Transforms loose tool collections into reliable, repeatable business processes.
Generate feature specifications by analyzing existing source code.
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.
Provides comprehensive guidance for Selenium WebDriver including browser automation, element location, waits, and test frameworks. Use when the user asks about Selenium, needs to automate web browsers, write Selenium tests, or work with Selenium WebDriver.
Prepares production launches. Use when preparing to deploy to production, setting up monitoring, planning staged rollouts, or needing a rollback strategy.
Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns.