Install and use the Agent Ready (agent-ready.dev) MCP server to scan any URL for AI agent-readability via MCP tool calls. Activates for "install agent-ready mcp", "set up agent-ready in Claude Desktop / Cursor / Cline / Goose / Continue", "add agent-ready as an MCP tool", "scan this site via agent-ready", "run scan_site / get_scan / ask via MCP". Pick this skill when the user wants tool-native access to Agent Ready — no curl, no fetch wiring. For direct REST access without MCP, use the `agent-ready-api` skill instead.

Use the Agent Ready (agent-ready.dev) command-line client to scan any public URL for AI agent-readability against the Vercel Agent Readability Spec, the llmstxt.org standard, and agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). Activates for "scan this site with the agent-ready CLI", "run agent-ready scan {URL} in the terminal", "agent-ready get {id}", "agent-ready list", "agent-ready ask {question}", or any time the user wants a one-command terminal scan with no fetch wiring and no MCP install. Pick this skill when the agent can run shell commands. For raw HTTP, use the `agent-ready-api` skill; for MCP-native tool calls, use `agent-ready-mcp`.

Use the Agent Ready (agent-ready.dev) REST API to scan any public URL for AI agent-readability against the Vercel Agent Readability Spec, the llmstxt.org standard, and agent-protocol manifests (MCP server cards, A2A, agents.json, agent-permissions.json, UCP, x402, NLWeb). Activates for "scan this site for AI agent-readability", "run an Agent Ready scan on {URL}", "check the Agent Ready score for {URL}", "what's the agent-readability rating for {URL}", or any time the user wants a programmatic readability scan via HTTP. Picks this skill when the user does NOT have the Agent Ready MCP server installed — for MCP, use the `agent-ready-mcp` skill instead.

PCB 공정 디지털트윈 플랫폼 페이지별 적합성 분석 및 보강 기능 가이드

PCB 대시보드 페이지 목록 및 기능 분석 문서. 각 페이지의 URL, 접근 권한, 렌더링 방식, 핵심 기능을 정리한 레퍼런스.

A cross-browser wrapper for the Web Audio API which aims to closely follow the standard.

Instrument applications with the OpenTelemetry SDK and prove the telemetry is good by validating it against a local Kopai backend. Use when setting up observability, adding tracing/logging/metrics, deciding what to instrument or which attributes to add, retrofitting OTel into an existing codebase, threading context through call chains, configuring sampling, or when traces/logs/metrics aren't appearing after setup. Also use when users say things like "my traces aren't showing up", "I don't see any data", or "how do I add observability to my app". Do NOT use to investigate existing telemetry for a root cause (use root-cause-analysis), to build dashboards (use create-dashboard), or to instrument LLM and agent calls (use otel-genai-instrumentation).

Testing the --bump flag

Git commit message format, types, and conventions

BC SaaS performance patterns, data access optimization, and best practices

Azure Functions and Logic Apps integration from Business Central AL

Custom telemetry with Feature Telemetry and Session.LogMessage for BC

Dependency injection, polymorphism, and plugin architectures in AL

File attachments, XMLport, and Azure Blob Storage patterns for Business Central

Create custom API pages (CRUD) and API queries (read-only joins) in AL

Consume Microsoft standard Business Central APIs (v2.0) - no AL coding required

Cue tiles, Activities CardPart, and FlowFields with drill-down for BC Role Centers

Dynamic event subscriber activation with BindSubscription in Business Central

OAuth 2.0 Client Credentials and Authorization Code flows for Business Central

Control AL object visibility with Access property (Public, Internal, Protected, Local)