10K skills · sorted by relevance
Inspect repository code or code changes for plausible security vulnerabilities. The skill records candidate issues with affected locations, attacker-controlled inputs, failing safeguards, and possible impact, preserving the evidence needed for later validation.
Check structured medical study materials, including guideline summaries, exam preparation, and insurance policy notes, before delivery. The skill validates required headings, source links, and scope statements, then guides corrections when the format fails validation.
Validate Claude Ads data contracts, scoring inputs, run outputs, installation procedures, and release readiness. Return machine-readable pass or fail results with evidence, the most urgent blocker, and recovery steps, while checking source freshness and safe removal boundaries.
Design an OpenRig agent team around a project goal. Create team and agent specifications, role guidance, and collaboration rules, then validate the setup and diagnose problems with startup instructions or agent coordination.
Validate security patches by comparing vulnerable and patched code against exploit tests, related attack variants, and normal behavior. Produce reproducible logs showing remaining flaws, regressions, newly introduced security failures, and gaps that still need testing.
Examines code or code changes for plausible security vulnerabilities by tracing attacker-controlled input to dangerous operations or failed safeguards. Records candidate issues with affected locations, supporting evidence, potential impact, and controls that need further validation.
Check a Proofpack release candidate before packaging by running tests, validating the candidate, and inspecting the package locally. Compare the source state and command results with the evidence log, then report passed, failed, or unknown checks.
Coordinate feature development from product direction through architecture, planning, validation, and implementation. Run the whole workflow or start at a selected stage, with saved decisions, review checkpoints, and a final pull request.
Build forms with Formik and yup, a library for defining input validation rules. Apply field errors, submission feedback, edit detection, and step-specific validation to login screens, editing forms, and forms split across multiple steps.
Build Claude Code plugin hooks: automated checks triggered by tool use or session events. Get guidance on prompt and command hooks for validating actions, checking task completion, loading context, and testing configurations.
Publish gh-aw changes as a draft pull request from a GitHub Copilot cloud agent. The workflow checks repository templates, runs required local validation, commits and pushes through runtime tools, and records the validation results in the PR.
Guides Apache OpenDAL release managers through preparation, release candidates, verification, voting, and publication. It tracks the current stage, checks external systems, and distinguishes core, candidate, and package versions when deciding the next release action.
Turn validated vulnerabilities into clear bug bounty reports for HackerOne, Bugcrowd, Intigriti, or Immunefi. Platform templates help organize demonstrated impact, reproducible steps, supporting evidence, severity reasoning, and concrete fixes in language reviewers can follow.
Validate substantial Rust changes by running the repository’s prescribed checks in order. Handle check failures, review formatting changes, and report which commands ran and whether validation passed before handing the work back.
Build Claude Code plugin hooks: automated checks triggered by tool use or session events. Get guidance on prompt and command hooks for validating actions, checking task completion, loading context, and testing configurations.
Draft a pull request description that explains the problem, implementation, trade-offs, and testing. It combines source-backed reasoning, validated Mermaid diagrams, and actual validation output into one Markdown file reviewers can assess on its own.
Assess candidate CVEs, identifiers for known vulnerabilities, against observed software, versions, and patch evidence. The skill helps determine whether to continue verification, gather more information, or change testing direction within the authorized scope.
Match identified products and versions against CVEs, records of known security vulnerabilities. Assess relevance, evidence quality, and patch status, then produce a candidate list to guide further investigation without attempting exploitation.
Evaluate trained machine learning models using metrics suited to the task. Compare candidates consistently, review decision thresholds and probability estimates, and identify weaknesses in validation before deployment or publication.
Authors, validates, and troubleshoots AWS CloudFormation templates. Covers template authoring with secure defaults, local validation with either cfn-lint or cloudformation-validate, cfn-guard security and compliance checks as a recommended default, account-aware CloudFormation service pre-deployment validation, CloudFormation Express mode for faster deployments, and root-cause diagnosis of failed stacks using CloudFormation events and CloudTrail correlation. Also covers author-time template intelligence with the CloudFormation Language Server and published cloudformation-validate libraries.
The English summary is being prepared. Showing the original description.
Discover and validate Agent Skills, host plugins and subagents, MCP servers and configurations, hooks, and marketplace catalogs against the correct authority. Use when performing pre-merge review, external submission checks, portability audits, security checks, or validation of mixed agent-system repositories. Trigger with "validate this skill", "audit this plugin", "check this agent", "review this MCP config", or "is this marketplace ready".
The English summary is being prepared. Showing the original description.
Working pattern for enterprise-edition features in Grida — the commercial/hosted concerns (entitlement, BYOD, billing) on top of the OSS core. Anchor for the `GRIDA-EE: <surface>` grep marker, `(ee)` route group, `*-hosted` package suffix, and namespaced `grida_*` schema. Use when adding or touching an EE-only feature, or deciding whether a feature is EE territory. Surface skills (`platform-consumers`) are siblings.
The English summary is being prepared. Showing the original description.
Grida Desktop Electron shell and release-impact work: BrowserWindow, preload, `window.grida`, menus, protocol/deep links, file associations, Forge, path-scoped bridge security, Electron-only UI bugs, and CDP / Playwright verification. Use for `desktop/`, `editor/app/desktop/**`, `editor/scaffolds/desktop/**`, `editor/lib/desktop/**`, `/desktop/*` CSP, GRIDA-SEC-004, and deciding whether linked-package or hosted-renderer changes require a native Desktop version bump or coordinated release. For implementing daemon/agent-tenant core behavior, use `agent-system` as well.
The English summary is being prepared. Showing the original description.
Doctrine for designing and evolving any **SDK** Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface rejects the wrong contents and keeps the package testable in isolation. Default is "core, not customizable"; customization is the exception, defended by a deciding table. Use when authoring or evolving any such surface — `@grida/*` published packages, engine crates (gridaco/nothing `crates/*`) published or FFI-exported, intent/message vocabularies, any contract a second author will compile against. Internal-only helper packages are welcome to follow, not forced. Companion skill for two-sided contract work: $sdk-seam. Critique partners: $pedantic, $etiology. Related: $naming.
The English summary is being prepared. Showing the original description.