manykarim

Explain Robot Framework keywords and their arguments from library/resource/suite documentation. Use when asked how to use a keyword, what arguments it takes, or to retrieve detailed keyword docs from libdoc across one or more libraries/resources.

Search Robot Framework library/resource/suite documentation to find matching keywords for a use case. Use when asked to find keywords, search libdoc, match a use case to keywords, or scan multiple libraries/resources for relevant keywords.

Guide AI agents in creating native desktop UI tests with PlatynUI (new_core) using the PlatynUI.BareMetal library — cross-platform desktop automation over Windows UIA and Linux AT-SPI2 with an XPath query model. Use when asked to automate desktop applications (windows, buttons, menus, text fields), locate native UI elements by XPath, or write Robot Framework tests with PlatynUI.

Generate Robot Framework test cases from structured requirements or scenarios. Use when asked to create test cases, apply tags/setup/teardown/templates, or produce keyword-driven tests.

Explain Robot Framework keywords and their arguments from library/resource/suite documentation. Use when asked how to use a keyword, what arguments it takes, or to retrieve detailed keyword docs from libdoc across one or more libraries/resources.

Search Robot Framework library/resource/suite documentation to find matching keywords for a use case. Use when asked to find keywords, search libdoc, match a use case to keywords, or scan multiple libraries/resources for relevant keywords.

Guide AI agents in creating native desktop UI tests with PlatynUI (new_core) using the PlatynUI.BareMetal library — cross-platform desktop automation over Windows UIA and Linux AT-SPI2 with an XPath query model. Use when asked to automate desktop applications (windows, buttons, menus, text fields), locate native UI elements by XPath, or write Robot Framework tests with PlatynUI.

Generate Robot Framework test cases from structured requirements or scenarios. Use when asked to create test cases, apply tags/setup/teardown/templates, or produce keyword-driven tests.

Author compact canonical source for an ARCHITECTURE review (artifact_type architecture-review) — decisions, constraints, interfaces, deployment context, alternatives, and interaction diagrams. Produces content-only YAML/JSON validated against the base + architecture overlay schema; render with render-branded-html. Use for architecture/engineering reviews.

Author compact canonical source for a PRD review (artifact_type prd-review) — business goals, out-of-scope, requirement coverage, stakeholders, readiness. Produces content-only YAML/JSON validated against the base + PRD overlay schema; render with render-branded-html. Use for product/delivery PRD reviews.

Deterministically render validated canonical review-doc source (YAML/JSON) into a single self-contained branded HTML file, with three layout skins (docs-site, editorial, brief), light/dark/auto mode, a widget section library, interactive or frozen Mermaid with fullscreen zoom, and optional PDF. Use when a review artifact's canonical source is ready and you need the styled HTML/PDF output. The model authors content; this renderer owns all chrome.

Entry point for producing a branded review document. Classifies the request into one of five artifact types (user-story, architecture, PRD, risk-analysis, test-charter), gathers evidence scope, delegates content authoring to the matching artifact skill, and renders/validates the result. Use when someone asks for a reviewable, company-themed doc from analysis (e.g. "make an architecture review", "turn this into a risk register HTML").

Author compact canonical source for a RISK ANALYSIS review (artifact_type risk-analysis) — risk matrix, triggers, controls, residual risk, owners, review cadence. Produces content-only YAML/JSON validated against the base + risk overlay schema; render with render-branded-html. Use for QA/product/operations risk reviews.

Author compact canonical source for an exploratory TEST CHARTER (artifact_type test-charter) — missions, heuristics, coverage boundaries, exit criteria, states explored. Produces content-only YAML/JSON validated against the base + test-charter overlay schema; render with render-branded-html. Use for QA exploratory-testing charters.

Author compact canonical source for a USER STORY review (artifact_type user-story-review) — acceptance criteria, personas, journey states, dependencies, scope gaps. Produces content-only YAML/JSON validated against the base + user-story overlay schema; render with render-branded-html. Use for PM/design story reviews.

Validate canonical review-doc source and rendered HTML across layers — JSON Schema, Mermaid syntax/render, accessibility (Axe/WCAG AA), responsive layout, and print/PDF. Use before sharing or committing a branded review artifact, in CI, or as a pre-commit hook.

Robot Framework Browser Library reference — Playwright-based browser automation with deep selector support. Use when authoring or refactoring browser test cases that target the Browser library (not SeleniumLibrary).

Search Robot Framework library/resource/suite documentation to find matching keywords for a use case. Use when asked to find keywords, search libdoc, match a use case to keywords, or scan multiple libraries/resources for relevant keywords.

A minimal, well-formed skill used as the security-scanner happy path.

Skill whose installer script demonstrates the `curl ... | sh` antipattern.

Demonstrates a prompt-injection payload embedded in the body.

Demonstrate a minimal valid Agent Skill used by AgentGuard's own tests.

Guide AI agents in creating Browser Library tests using Playwright-powered automation with auto-waiting, assertion engine, and modern web features. Use when asked to create web tests with Browser Library, handle locators, assertions, iframes, Shadow DOM, or multi-tab scenarios.

Parse Robot Framework output.xml results into JSON summaries, detailed suite/test breakdowns, tag and criticality stats, execution errors, failed test messages, keyword-level errors, and timing. Use when asked to read/merge output.xml, compute pass/fail counts, tag stats, criticality, error messages, elapsed time, slowest tests/keywords, or combine/merge multiple outputs via rebot.

Triage and permanently fix Robot Framework test failures recorded by robotframework-heal. Use after a test run when heal events exist (an `events.jsonl` in the run's heal report directory), to review healed/unhealed failures, inspect root causes, and apply locator fixes to .robot/.resource files safely.