Showing 31981–32010 of 77104 skills
在 WorkBuddy/宿主应用的内嵌智能页(Smart Page)上代替用户完成表单提交(报名、投稿、登记、问卷),当用户说『帮我提交』『代填并提交』『帮我在活动页报名』『这个表单替我填』时必须使用此技能。也适用于:页面表单只存在于宿主应用 webview 内、无头浏览器点不到按钮、页面 JS 里有 submitWork/saveWork 之类的保存函数但找不到对应后端接口、写入报 permission denied / 12607 / not login 时定位正确的写入通道。核心能力是通道权限模型判定 + 宿主 HTTP 面逆向 + 写后回读复核(false-success defense)+ 写入授权边界与红线字段拦截(授权/承诺类字段禁止代填)+ 幂等查重防重复提交。不适用于普通公开网页表单(用浏览器自动化即可)与本地 Excel/CSV 批量导入。
xinetzone/SpecWeave
当用户提到'链接检查'、'检查链接'、'断链'、'链接修复'、'fix links'、'check links'、'验证链接'、'死链'、'链接有效性'、'提交前检查'时,必须使用此技能。提供Markdown链接有效性检查与自动修复能力:本地文件引用验证、外部URL可达性检测、file:///绝对路径转相对路径、相对路径层级自动校正。不要手动查找断链——本Skill封装了缓存机制、并发检测、自动修复和dry-run预览,是提交前质量门禁的核心工具。
xinetzone/SpecWeave
审计 Skill 登记面的分类计数漂移:把 .agents/skills/README.md 与 .agents/capability-registry/02-skills.md 每个分类标题声明的(N个)与该节实际表格数据行逐一比对,先自证计数器再下结论,区分表头漂移、多子表求和与跨面缺行三类,缺行只报告不擅改。当用户提到「登记面计数漂移」「表头数字和行数不一致」「README 与 registry 数量对不上」「命令集门面 11/10」「审计分类计数」「count drift」「核对(N个)」时必须使用此技能;不用于执行四处登记(用 native-skill-surface-registration),不用于判断推荐动作(用 skill-recommendation-disk-triage)。
xinetzone/SpecWeave
Ask which skill or flow fits your situation. A router over the skills in this repo.
JesusFilm/core
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
JesusFilm/core
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
JesusFilm/core
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
JesusFilm/core
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
JesusFilm/core
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
JesusFilm/core
Teach the user a new skill or concept, within this workspace.
JesusFilm/core
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
JesusFilm/core
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
JesusFilm/core
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
JesusFilm/core
Use when auditing a user-facing app — web, mobile (iOS/Android/React Native/Flutter), desktop, CLI, or games — for accessibility barriers or WCAG 2.2 conformance, before shipping UI changes, or in response to concerns about screen-reader, keyboard, low-vision, motor, cognitive, or photosensitive users. Not for general bug hunting or code correctness.
Ovid/paad
Use when assessing the architectural health of a codebase — before a major refactor, when onboarding to an unfamiliar repo, after rapid growth, when planning a redesign, or to surface structural strengths and risks before they become expensive. Not for fixing what it finds, and not for reviewing a branch diff.
Ovid/paad
EXPERIMENTAL. Use when looking for meaningfully duplicated logic in a codebase, especially duplicate behavior hidden behind different names, different syntax, different control flow, or independently evolved implementations. Not for style issues, not for syntactic clone detection, and not for fixing what it finds.
Ovid/paad
EXPERIMENTAL. Use when code needs a security review against the OWASP Top 10:2025 — access control, misconfiguration, supply chain, cryptography, injection, insecure design, authentication, integrity, logging and alerting, and mishandled exceptional conditions. Not for penetration testing a running system, not for infrastructure-only scanning, and not for fixing what it finds.
Ovid/paad
Use when reviewing current branch for bugs before pushing or merging, when wanting a thorough multi-agent review of local changes, or when preparing work for human review. Not for codebase structure, not for code style, and not for fixing what it finds.
Ovid/paad
Use when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope creep, or design drift between intent and action documents. Needs both documents; not for checking code against a spec.
Ovid/paad
EXPERIMENTAL. Use when working the project-wide out-of-scope backlog at .reviews/code/backlog.md and .reviews/security/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is the agentic-review skill — and not for reviewing a branch diff.
Ovid/paad
Use when working through architectural flaws documented in a .reviews/architecture/ report — selecting which flaws to fix, resuming a partial fix session across multiple sittings, or applying structural changes that need to be tracked back to a report. Not for producing that report — run the agentic-architecture skill first if there isn't one.
Ovid/paad
Use when a session is running out of context and the work needs to continue in a fresh one, or when starting a session meant to pick up where an earlier one stopped. Not for compacting in place — that is /compact — and not for specifying work that has not started, which is a plan.
Ovid/paad
Use when reviewing a spec, PRD, requirements doc, or design plan before implementation begins — especially when the doc feels too big, bundles unrelated features, may contradict the current codebase, or seems vague, infeasible, or thin on security and error handling. Not for cross-checking a spec against a plan — that's the alignment skill.
Ovid/paad
Use when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is the pushback skill.
Ovid/paad
Analyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.
Ovid/paad
Use when making a small, quick change — a bug fix, typo, minor feature, tweak, or anything the user calls "vibe coding" — that looks like 1-3 files in the same module
Ovid/paad
Interactive logo & brand design strategist. Runs a strategy workshop, narrows a creative direction, lands a single centralized concept, then outputs a condensed branding table plus 10+ logo ideas with rationale. Use when the user wants to design a logo, develop a brand identity, write a logo brief, brainstorm logo concepts, or run brand strategy before sketching. Triggers include "design a logo", "logo ideas", "brand identity", "help me with my logo", "logo brief", "what should my logo be".
posva/dotfiles
Maintain the Abbey / Aviva / Abi Discord system prompts in the Rust abbey-bot (`src/ask.rs`) and keep the hosted Grok bots (Grok Bot Abbey, Aviva Grok) in step with them. Use when the user says "improve grok bots", "abbey prompt", "persona prompt", "ask.rs", "system prompt", "tip floor", asks to change how Abbey/Aviva/Abi speak on Discord, or after an abbey-bot PR merges and the hosted bot's tip floor needs bumping. Runs as /abbey-system-prompt.
donaldfilimon/abi
Synchronize ABI Markdown and docs claims with executable behavior. Use before editing README, AGENTS.md, CLAUDE.md, GEMINI.md, docs/**/*.mdx, walkthroughs, changelogs, or any old ABI Markdown that mentions WDBX, MCP, GPU, clustering, compression, FHE, agents, or benchmarks.
donaldfilimon/abi
Constitution governance superpower. 6-principle response audit with E-score, veto, and surfaced telemetry.
donaldfilimon/abi