912 skills · sorted by relevance
Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.
[omh] Unsure whether Codex or Claude Code is ready: executor runtime readiness - compare Codex, Claude Code, Hermes coding, and oh-my runtimes by tools and handoff mode; use external-connector-readiness for a named plugin or API, and toolbelt-readiness for the whole capability inventory. Use when the user says: executor-runtime-readiness, executor readiness, runtime readiness, codex readiness, claude code readiness, hermes coding readiness, executor tools, missing tools.
The English summary is being prepared. Showing the original description.
[omh] Evaluating a plugin, connector, or API for adoption: external connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use executor-runtime-readiness for coding-owner choice and toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
The English summary is being prepared. Showing the original description.
[omh] Evaluating a plugin, connector, or API for adoption: external connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
The English summary is being prepared. Showing the original description.
[omh] Which tools and credentials a workflow needs: inventory which MCP servers, CLIs, APIs, credentials, and connectors a workflow needs; use external-connector-readiness to assess one named integration and executor-runtime-readiness to choose the coding owner. Use when the user says: toolbelt-readiness, mcp readiness, tool readiness, plugin readiness, connector readiness, needed mcp, api credential, missing cli.
The English summary is being prepared. Showing the original description.
Assess a repository's readiness for an AI agent execution framework across five dimensions. Produce JSON or a table with readiness scores, estimated cost per run, and scaffold status, without changing repository files.
[omh] Which tools and credentials a workflow needs: inventory which MCP servers, CLIs, APIs, credentials, and connectors a workflow needs; use external-connector-readiness to assess one named integration. Use when the user says: toolbelt-readiness, mcp readiness, tool readiness, plugin readiness, connector readiness, needed mcp, api credential, missing cli.
The English summary is being prepared. Showing the original description.
[omh] Agent control of a robot, 3D printer, or IoT relay: gate robots, 3D printers, IoT relays, sensors, and lab hardware before trials; use external-connector-readiness for provider or connector adoption and toolbelt-readiness for missing control tools. Use when the user says: physical-device-readiness, physical device readiness, device safety readiness, physical device safety, hardware safety gate, 3d printer readiness, 3D printer safety, snapmaker printer safety.
The English summary is being prepared. Showing the original description.
Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.
Review readiness across multiple compliance frameworks using six focused questions. Identify overlapping evidence, missing owners, audit scheduling conflicts, and mock audit findings, then produce a readiness verdict with three actions, owners, and deadlines.
[omh] Importing prompt files for Hermes: prompt import readiness - review and normalize external CLI-agent prompt files before offering slash-command candidates; use external-connector-readiness for plugin or API adoption and toolbelt-readiness for missing runtime capabilities. Use when the user says: prompt-import-readiness, prompt import readiness, slash prompt import, slash prompts import, slash command prompt import, prompt library import, prompt folder import, prompt directory import.
The English summary is being prepared. Showing the original description.
Assess whether an application is ready for production using local files and authorized evidence. Reviews authentication, data, payments, and operations, then reports release blockers, prioritized fixes, and a readiness score without uploading repository contents to an external audit service.
Prepare a specified software version for release by checking version consistency and changelog readiness, building packages, and testing basic behavior. Produce checksums, release notes, and a readiness report; public release actions require separate authorization.
Review an AI system's EU AI Act readiness through six structured questions. Produce an article-cited assessment covering risk classification, conformity checks, organizational obligations, transparency, and general-purpose models, with gaps and three prioritized actions.
Review SOC 2 Type II audit readiness through six questions about controls, the organizational safeguards assessed over an observation period. Identify evidence gaps, control changes, and exceptions, then organize readiness findings and three concrete next actions.
Audit a website against the Forter Agentic Readiness Guide. Loads the 25 weighted rubrics in `audit/`, probes the target site (and optional source code), scores each guideline Pass/Partial/Fail/N/A with sub-check granularity, and produces a prioritized fix report. Use when a user asks "score my site against the agentic readiness guide", "audit https://… for agent readiness", or "what do I need to fix to be agent-ready".
The English summary is being prepared. Showing the original description.
Maps every proposed P&ID object from an accepted enrichment draft to the generic family, catalogue class and required attributes the project's intelligent P&ID authoring tool would need, as a readiness table with UNKNOWN wherever the project catalogue extract is not provided, plus connectivity readiness per line and a numbered list of import blockers. Mapping only: it never writes to the tool, never produces an import file and never claims a class exists in the catalogue. Use when the user asks to "build the readiness map", "show how far the draft is from a sandbox import", "list what would block the import", "map the objects to the tool catalogue" or "check attribute readiness against the catalogue extract" after gate G3. Do not use for validating the discipline sections or assembling the review package, use validation-and-review-package instead. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.
Helps prepare web applications for production with automated testing and deployment workflows, Docker packaging, health checks, and rollback plans. Provides examples and checklists for choosing release strategies and reviewing readiness before launch.
Assess a repository without changing it and report its type, suggested agent roles, risk, MCP connections, test confidence, and publication readiness. Use the results for setup decisions, comparisons over time, or automated risk checks in CI.
Build pre-session diagnostic workflows with Zoom Probe SDK to check browser support, media permissions, audio, video, and network readiness. Reference patterns cover diagnostic pages, live statistics, structured reports, and readiness checks before joining.
Prepare for ISO 27001 audits by reviewing six areas of an information security management system: audit coverage, risks, access, suppliers, incidents, and management reviews. Summarize evidence gaps, readiness, and three priority actions with owners and timelines.
Assess whether a GKE cluster or application is ready for production. Coordinates specialist skills to review scaling, security, reliability, monitoring, recovery, costs, and maintenance, then reports domain status, a weighted readiness score, and remediation priorities.
Combine Convex authorization, code quality, performance, and failure audits into one readiness report. It removes duplicate findings, scores confirmed issues with a stated formula, and orders the fixes while clearly identifying checks that could not run.
[omh] Imminent production launch or release: evaluate release, deploy, security, observability, rollback, docs, and support readiness without claiming production access. Use when the user says: production-audit, production audit, production readiness, prod audit, prod readiness, ready for production, ready to ship, ship readiness.
The English summary is being prepared. Showing the original description.