6 tagged annotations, measured the same way as everything else here.
Browse within: ai-tools 24annotation 24feedback-loop 12hypothesis-testing 12llmops 12regression-testing 12systematic-evaluation 12Zotero 6filter 6links 6weavero 6zotero-plugin 6
Skill Claude CodeCodex
Design, run, and analyze AI test suites on Rhesis — explore endpoints, build test foundations from a spec, create requirements and metrics, execute tests, and analyze results. Use when testing an AI endpoint, pasting a Product Requirements Document (PRD) or product spec, or working with Rhesis via MCP.
Skill Claude Code
ALWAYS use this skill when the user asks to build, modify, or audit a FrontMCP tool. Covers everything inside @Tool({...}): class and function-style tools, Zod input/output schemas with derived execute() types, dependency injection (this.get / this.tryGet), error handling (this.fail, MCP error classes), throttling…
Skill Claude CodeCodex
AI guardrails and coding rules generated by VibeTags from @AILocked, @AIContext, and related annotations. Load this skill when writing, reviewing, or modifying code in this project.
Skill Claude Code
Run the standard markdown review loop end-to-end with the mdxg-redline CLI: send a markdown document to a human reviewer, wait (via Bash polling) for the feedback.json they export, then apply their location-aware inline comments back into the markdown and revise it. Always use this skill when the user wants…
Skill Claude CodeCodex
Use decor-cli to decorate screenshots, images, and videos with backgrounds, gradients, templates, annotations, arrows, shapes, counters, and spotlight effects from CLI or MCP.
Skill Claude CodeCodex
Use this skill on every UI turn that touches composition — building, modifying, restructuring, or annotating any page, component, route, form, layout, navigation, modal, focus behaviour, or live region. Make sure to use this before any UI code change, and whenever the user asks what an a11y.md captures. Triggers on…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: