Sentry
- 254 skills
- 0 followers
- 46k repo stars
- 28 verified
- 3 days ago last updated
- ▌ Tts · getsentry bundleGenerates spoken narration with Gemini TTS through Vercel AI Gateway. Use for text-to-speech, audio samples, voiceovers, or speaking as Junior with the reusable Junior voice. Do not use for transcription, voice cloning, music generation, or rendering a video without a narration request.
- ▌ Figma · getsentryRead Figma designs through the read-only Figma REST API. Use when users share a Figma link or ask Junior to look at a Figma frame, match a design, pull exact spacing, colors, typography, copy, or component details, render a frame as an image, compare an implementation against a design, or read comments on a Figma file. Do not use it to edit Figma files, post Figma comments, or for screenshots or general UI work with no Figma link.
- ▌ Xdotcom · getsentryRead public X (Twitter) data through the read-only X API v2. Use when users share an x.com or twitter.com link, or ask what someone posted on X, what people are saying about a topic, product, or launch on X, how much chatter something got, or for a post's text, metrics, replies, or an account's recent posts. Do not use it to post, reply, like, repost, follow, or send DMs, or to read private or protected data.
- ▌ Pagerduty · getsentryLook up PagerDuty on-call state through the read-only PagerDuty REST API. Use when users ask who is on call, who is rotating in or out, when the next on-call handoff is, what a schedule or escalation policy looks like, which team or service owns paging, or for PagerDuty incident status and timelines. Do not use it to acknowledge, resolve, reassign, or create incidents, to create schedule overrides, or for Sentry issues, Datadog telemetry, or Linear tickets.
- ▌ Demo Video · getsentry bundleCreates and revises edited videos with Remotion, such as product demos, narrated screen walkthroughs, animated explainers, and short presentations built from browser captures, with optional narration, captions, and music. Use when asked to make, animate, polish, or update a video or presentation of an app or shipped work. Do not use for a raw browser recording, screenshot-only visual QA, or audio-only text-to-speech.
- ▌ Integrity Review · getsentry bundleFinds code changes that would harm the organization shipping them through their own behavior or that hide what they do. Use for change integrity review, sabotage or insider-risk review, destructive operations, logic or time bombs, install and build hooks, dependency and registry tampering, disabled tests or security tooling, audit logging removal, infrastructure privilege grants, obfuscated or encoded code, misleading comments, text aimed at automated reviewers, and changes outside a pull request's stated scope.
- ▌ Craft CLI · getsentry bundleUse Craft CLI to inspect release configuration and workspaces, prepare releases and changelogs, inspect artifacts, or publish to configured package registries. Use for Craft release workflows and .craft.yml questions; not for general Sentry issue investigation or ordinary app builds.
- ▌ Relay Conformance Audit · getsentry bundleAudit the Cocoa SDK for protocol-conformance drift against Relay (getsentry/relay) — hard-coded strings/wire formats that must match Relay exactly and fail silently when they don't (the class behind
- ▌ MCP QA 2 · getsentryQA MCP tool changes with local CLI and real agent clients. Use when explicitly invoked via /mcp-qa or when asked to QA MCP tool changes end-to-end.
- ▌ Testing Guidelines 3 · getsentryGuide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
- ▌ Logging Observability 2 · getsentryReview code for correct logging and error handling patterns. Use when reviewing code that handles errors, uses logging functions, or captures exceptions. Enforces the error hierarchy where 4xx errors are never logged to Sentry and 5xx errors always are. Trigger phrases include "review logging", "check error handling", "audit observability", or verify correct use of logIssue vs logError.
- ▌ Sentry CLI 2 · getsentry bundleGuide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
- ▌ Mobilebuildmcp · getsentryOfficial skill for MobileBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
- ▌ Mobilebuildmcp CLI · getsentryOfficial skill for the MobileBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
- ▌ Mobilebuildmcp Docs Command Review · getsentryUse when reviewing MobileBuildMCP changelog CLI command references for invalid current guidance while allowing historical migration examples.
- ▌ Mobilebuildmcp Docs Release Review · getsentryUse when reviewing MobileBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes.
- ▌ Mobilebuildmcp Test Boundary Review · getsentryUse when reviewing MobileBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries.
- ▌ Mobilebuildmcp Tool Contract Review · getsentryUse when reviewing MobileBuildMCP tool contract changes across implementation, manifests, workflow membership, output schema metadata, and next-step templates.
- ▌ Mobilebuildmcp Runtime Boundary Review · getsentryUse when reviewing MobileBuildMCP runtime boundary changes across MCP, direct CLI invocation, daemon-routed tools, and Xcode IDE bridge routing.
- ▌ Mobilebuildmcp Snapshot Fixture Review · getsentryUse when reviewing MobileBuildMCP snapshot fixture changes for MCP, CLI, and JSON output contract integrity.
- ▌ Mobilebuildmcp Structured Output Review · getsentryUse when reviewing MobileBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility.
- ▌ Mobilebuildmcp Packaging Resource Review · getsentryUse when reviewing MobileBuildMCP packaging, resource-root, build artifact, bundled AXe, schema, manifest, and portable macOS distribution changes.
- ▌ Mobilebuildmcp Rendering Streaming Review · getsentryUse when reviewing MobileBuildMCP rendering, streaming fragment, next-step, and CLI output mode changes for boundary violations.
- ▌ Skill Creator 2 · getsentryAlias for sentry-skills:skill-writer. Use when users explicitly ask for "skill-creator" or reference the legacy skill name. Redirects to the canonical skill authoring workflow.
- ▌ Dotagents 2 · getsentry bundleManage agent skill dependencies with dotagents. Use when asked to "add a skill", "install skills", "remove a skill", "update skills", "dotagents init", "agents.toml", "agents.lock", "sync skills", "list skills", "set up dotagents", "configure trust", "add MCP server", "add hook", "wildcard skills", "user scope", or any dotagents-related task.
- ▌ Triage Issue 2 · getsentry bundleTriage GitHub issues with codebase research and actionable recommendations
- ▌ Skill Scanner 2 · getsentry bundleScan agent skills for security issues. Use when asked to "scan a skill", "audit a skill", "review skill security", "check skill for injection", "validate SKILL.md", or assess whether an agent skill is safe to install. Checks for prompt injection, malicious scripts, excessive permissions, secret exposure, and supply chain risks.
- ▌ Skill Writer 2 · getsentry bundleCreate, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, depth gates, authoring, registration, and validation.
- ▌ Security Review 2 · getsentry bundleFinds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
- ▌ Code Review 2 · getsentry bundleFinds real correctness bugs in code changes. Use for adversarial code review, bug hunts, regression review, PR correctness review, logic errors, data loss, race conditions, state bugs, interface contract breaks, error handling bugs, edge cases, broken builds, or broken workflows. Excludes style, readability, architecture, AppSec, and best-practice-only feedback unless the issue causes a demonstrable bug.
- ▌
- ▌ Sentry Svelte Sdk 2 · getsentry bundleFull Sentry SDK setup for Svelte and SvelteKit. Use when asked to "add Sentry to Svelte", "add Sentry to SvelteKit", "install @sentry/sveltekit", or configure error monitoring, tracing, session replay, or logging for Svelte or SvelteKit applications.
- ▌ Sentry Create Alert 2 · getsentryCreate Sentry alerts using the workflow engine API. Use when asked to create alerts, set up notifications, configure issue priority alerts, or build workflow automations. Supports email, Slack, PagerDuty, Discord, and other notification actions.
- ▌ Sentry Sdk Skill Creator 2 · getsentry bundleCreate a complete Sentry SDK skill bundle for any platform. Use when asked to "create an SDK skill", "add a new platform skill", "write a Sentry skill for X", or build a new sentry-<platform>-sdk skill bundle with wizard flow and feature reference files.
- ▌ Sentry Otel Exporter Setup 2 · getsentryConfigure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation. Use when setting up OTel with Sentry, configuring collector pipelines for traces and logs, or routing telemetry from multiple services to Sentry projects.
- ▌ Sentry Go Sdk 2 · getsentry bundleFull Sentry SDK setup for Go. Use when asked to "add Sentry to Go", "install sentry-go", "setup Sentry in Go", or configure error monitoring, tracing, logging, metrics, or crons for Go applications. Supports net/http, Gin, Echo, Fiber, FastHTTP, Iris, and Negroni.
- ▌ Sentry Cocoa Sdk 2 · getsentry bundleFull Sentry SDK setup for Apple platforms (iOS, macOS, tvOS, watchOS, visionOS). Use when asked to "add Sentry to iOS", "add Sentry to Swift", "install sentry-cocoa", or configure error monitoring, tracing, profiling, session replay, or logging for Apple applications. Supports SwiftUI and UIKit.
- ▌ Sentry Dotnet Sdk 2 · getsentry bundleFull Sentry SDK setup for .NET. Use when asked to "add Sentry to .NET", "install Sentry for C#", or configure error monitoring, tracing, profiling, logging, or crons for ASP.NET Core, MAUI, WPF, WinForms, Blazor, Azure Functions, or any other .NET application.
- ▌ Sentry Setup AI Monitoring 3 · getsentrySetup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically detects installed AI SDKs and configures the appropriate Sentry integration.
- ▌ Write Tests 2 · getsentryWrite tests following project conventions. Use when adding new tests or modifying existing ones.
- ▌ Fix Security Vulnerability 2 · getsentry bundleAnalyze and propose fixes for Dependabot security alerts
- ▌ Sentry Get Started 2 · getsentry bundleGuided entry point for using Sentry through your agent. Orients you to your current setup and, for a new project, sets up Sentry end to end with sane defaults — provision a project, install the SDK (errors, tracing, and whatever it enables by default), and confirm real telemetry reaches Sentry. Routes other intents (adding more signals, fixing issues) to the right skill.
- ▌ Sentry Setup AI Monitoring 2 · getsentrySetup Sentry AI Agent Monitoring in any project. Use when asked to monitor LLM calls, track AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI/Pydantic AI. Detects installed AI SDKs and configures appropriate integrations.
- ▌ Testing Guidelines 2 · getsentryGuide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
- ▌ Effect 2 · getsentry bundleOpinionated guide for building production TypeScript applications with Effect v4. Use when implementing Effect workflows, services, layers, schemas, configuration, schedules, caches, streams, HTTP clients, or tests.
- ▌ Shadcn 2 · getsentry bundleManages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
- ▌ Pr 2 · getsentryCreate a draft PR for the current branch following repo conventions. Writes a concise PR description from the implementation plan, embeds the full plan as a hidden HTML comment so reviewers can read it without leaving GitHub, and reuses an existing branch when one is already checked out. Use this once your implementation is committed and pushed.
- ▌ Deslop 2 · getsentryStrip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.
- ▌
- ▌ Review 2 · getsentry bundleReview the current branch's changes against intent. Returns a structured list of findings the caller can hand to a fix-applier, or an empty list when there's nothing to address. Use this for both self-review of your own work and reviewing someone else's PR.
- ▌ Review Pr 2 · getsentryReview a pull request. Self-fix on own PRs, post a review on others'. Load repo-setup first.
- ▌ Auto Merge 2 · getsentryAuto-merge a PR after it is marked ready-for-review, if the change is small, non-disruptive, and all checks pass.
- ▌ Repo Setup 2 · getsentryRefresh /workspace/repo and prepare the correct branch. Load this before any situation skill.
- ▌ Apply Fixes 2 · getsentryApply review findings as the smallest code changes, then commit and push. Used on the bot's own PRs.
- ▌ Mark Pr Ready 2 · getsentryPromote a draft PR to ready-for-review after CI passes and self-review is clean. Assigns reviewers and adds labels.
- ▌ Resolve Issue 2 · getsentry bundleResolve a GitHub issue end-to-end — explore, plan, implement, clean up, and open a draft PR.
- ▌ Respond To Comment 2 · getsentryTriage and respond to comments on a PR. Fix if actionable, reply either way. Load repo-setup first.
- ▌ Architecture Review 2 · getsentryStaff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
- ▌
- ▌ Shadcn · getsentry bundleManages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
- ▌ Garfield 2 · getsentry bundleUse while implementing code changes, after a meaningful slice, to coordinate subagent review/fix/verify loops that preserve the core user or PR intent. Fix regressions, explicit requirement mismatches, validation gaps, and behavior-preserving cleanup; report unrelated improvements or out-of-intent behavior changes instead. Do not use for standalone reviews, brainstorming, or non-code iteration.
- ▌ Create Pr · getsentryCreate pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
- ▌ Vitest Evals · getsentry bundleUse when authoring, reviewing, or debugging harness-backed vitest-evals suites, custom Harness adapters, first-party ai-sdk or pi-ai harness integrations, judges, replay, reporter-facing normalized run data, or examples and docs for these APIs.
- ▌ Sentry Docs · getsentry bundleSentry documentation site (docs.sentry.io). Use for contributing to docs or understanding docs architecture. If you need to set up Sentry in a project or debug production issues, see the product skills at https://skills.sentry.dev.
- ▌ Docs Review · getsentryReview documentation for Sentry style and voice. Use when reviewing or writing user-facing documentation to ensure it follows the Sentry documentation style guide.
- ▌ Technical Docs · getsentryWrite and review technical documentation for Sentry SDK docs. Use when creating, editing, or reviewing documentation pages, especially MDX files in docs/platforms/.
- ▌
- ▌ Write Tip · getsentryCreate or improve AI productivity tips and guides for the Abacus dashboard. Use when writing new tips, editing existing tips, or reviewing tip content for quality. Ensures tips follow the established format with scenarios, prompts, and proper structure.
- ▌ DB Migrate · getsentryCreate database migrations using Drizzle Kit. Use when adding/modifying tables, columns, or indexes. Ensures schema.ts and migrations stay in sync.
- ▌ Write Docs · getsentryCreate or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly.
- ▌ Daily Update · getsentryGenerate a formatted async daily standup message for the Sentry SDK team channel. Use when asked to create a "daily update", "async daily", "standup update", or "async team update".
- ▌ Contributing Md · getsentryGenerate or align a CONTRIBUTING.md for a Sentry SDK repository with the develop.sentry.dev standard template. Use when asked to "create contributing.md", "update contributing.md", "align contributing docs", "standardize contributor docs", or when the contributing guide is outdated, missing sections, or does not exist.
- ▌ Linear Initiative · getsentryCreates Linear projects for SDK repositories based on a Linear initiative. Use when rolling out a feature across multiple SDKs, creating SDK projects from initiative, or setting up cross-SDK alignment work.
- ▌ Linear Type Labeler · getsentryClassify and apply Type labels to Linear issues based on their title and description.
- ▌ Span Convention Review · getsentryReview OpenTelemetry tracing span changes in SDK repositories for conformance to Sentry Conventions and OTel Semantic Conventions. Use when reviewing span instrumentation, "review spans", "check span conventions", "span review", "OTel span check", "tracing convention review".
- ▌ Sdk Feature Implementation · getsentry bundleImplement a feature across Sentry SDK repositories by spawning parallel agents. Use when you have Linear initiatives/projects/issues and want to create draft PRs. Triggers on "implement across SDKs", "spawn SDK agents", "SDK implementation", "parallel SDK implementation", "continue SDK rollout".
- ▌ Linear Sdk Telemetry Labeler · getsentryClassify and apply SDK Telemetry labels to Linear issues based on their title and description. Use when triaging issues related to SDK telemetry signals: errors, traces, spans, profiles, replays, logs, metrics, cron checks, client reports, user feedbacks, or attachments. Triggers: "sdk telemetry label", "telemetry labeler", "label telemetry issues", "tag telemetry".
- ▌ Wrdn Pii · getsentry bundleDetects real personally identifiable information, customer identifiers, and customer-confidential business data in code changes. Use when asked to find PII, customer IPs, real email addresses, revenue data, billing data, personal data, privacy leaks, customer info in logs, PII in URLs, or accidental production data in tests, fixtures, comments, docs, config, telemetry, or API responses.
- ▌ Wrdn Authz · getsentry bundleDetects authorization flaws: IDOR, missing ownership or tenant scoping, role checks that fail open, privilege escalation, unauthenticated admin actions, mass assignment, and token/session claims trusted for permission decisions. Use when asked to review route handlers, middleware, decorators, resolvers, RBAC/ACL logic, serializers, ORM queries, token-derived scopes, or admin surfaces.
- ▌ Vercel Deepsec · getsentry bundleDetects broad web application security vulnerabilities using the Vercel DeepSec benchmark prompt. Use when benchmarking security review coverage or running an open-ended appsec scan for auth bypass, missing auth, XSS, RCE, SQL injection, SSRF, path traversal, secrets, weak crypto, unsafe redirects, webhook verification, Next.js Server Actions, Lua/OpenResty, Go, cache poisoning, or header trust bugs.
- ▌ Wrdn Data Exfil · getsentry bundleDetects bugs where untrusted input reaches a sink that leaks data beyond its intended scope. Covers SSRF (including cloud metadata, internal services, image proxies), path traversal and archive zip-slip, SQL/NoSQL injection enabling bulk reads, XXE file read, response serializers over-exposing internal fields, verbose error pages, logs capturing secrets, and CSV/formula injection in exports. Run on any diff touching HTTP clients with user URLs, file I/O with user paths, raw queries, XML parsing, response serializers, error handlers, or export pipelines.
- ▌ Wrdn Dos Review · getsentry bundleFinds availability / denial-of-service bugs reachable from untrusted input — unbounded allocation, uncontrolled recursion, non-terminating loops, decompression bombs, panic/resource-leak, super-linear output amplification, algorithmic-complexity / ReDoS catastrophic regex backtracking, and bounds that are present but ineffective (wrong dimension, applied too late, under-counting cost, or defaulted off). Use for DoS and resource-exhaustion audits, CPU-complexity and cost-limit / quota-accuracy review, parser/decoder/deserialization hardening, and crash-safety review of code that processes attacker-controlled bytes.
- ▌ Wrdn Gha Workflows · getsentry bundleDetects exploitable GitHub Actions workflow vulnerabilities, including pull_request_target pwn requests, unsafe PR checkout, expression injection in run steps and actions/github-script blocks, workflow_dispatch and workflow_call input command injection, comment- and discussion-triggered commands, TOCTOU between approval and checkout, secret exposure, broad permissions, reusable workflows that consume undeclared secrets, ArtiPACKED-style token leaks through uploaded artifacts, cache poisoning and eviction-stuffing, supply-chain risk from unpinned third-party actions (tj-actions/changed-files class), and self-hosted runner abuse. Run on diffs touching .github/workflows, action.yml, action.yaml, repo-local actions, or CI-loaded scripts and config.
- ▌ Wrdn Code Execution · getsentry bundleDetects bugs where untrusted input reaches a sink that produces code or command execution on the server. Covers command/shell injection, unsafe deserialization, server-side template injection, eval/Function/vm reached by user data, XXE-to-RCE gadgets, and prototype pollution that lands on a code-executing sink. Run on any diff touching subprocess/exec calls, template rendering, deserialization of bytes, XML parsing, or deep-merge of user-controlled objects.
- ▌ Effect · getsentry bundleGuides production TypeScript work with current Effect APIs and explicit Effect architecture; use when implementing, reviewing, debugging, or refactoring Effect schemas, services, layers, config, schedules, caches, streams, HTTP clients, or tests, but not for non-Effect TypeScript or an explicitly older API surface.
- ▌ Garfield · getsentry bundleCoordinates subagent review, fixes, and verification during implementation; use when the user explicitly asks for Garfield on an active code slice, but not for standalone review, brainstorming, non-code work, or PR CI iteration.
- ▌ Skillet Authoring · getsentry bundleAuthors, improves, or migrates agent skills with the Skillet CLI; use when asked to create or write a skill, improve its instructions or evals, diagnose failing evals, or migrate a legacy SKILL.md, uppercase SPEC.md, or spec.yaml skill, but not when merely using an existing skill.
- ▌ Commit Conventions · getsentry bundleWrite disciplined git commits. Use whenever committing changes or writing commit messages — conventional-commit subjects, and never commit directly to main.
- ▌ Pr · getsentry bundleCreate a draft PR for the current branch following repo conventions. Writes a concise PR description from the implementation plan, embeds the full plan as a hidden HTML comment so reviewers can read it without leaving GitHub, and reuses an existing branch when one is already checked out. Use this once your implementation is committed and pushed.
- ▌ Deslop · getsentry bundleStrip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.
- ▌
- ▌ Review · getsentry bundleReview the current branch's changes against intent. Returns a structured list of findings the caller can hand to a fix-applier, or an empty list when there's nothing to address. Use this for both self-review of your own work and reviewing someone else's PR.
- ▌ Review Pr · getsentry bundleReview a pull request. Self-fix on own PRs, post a review on others'. Load repo-setup first.
- ▌ Auto Merge · getsentry bundleAuto-merge a PR after it is marked ready-for-review, if the change is small, non-disruptive, and all checks pass.
- ▌ Repo Setup · getsentry bundleRefresh /workspace/repo and prepare the correct branch. Load this before any situation skill.
- ▌ Apply Fixes · getsentry bundleApply review findings as the smallest code changes, then commit and push. Used on the bot's own PRs.
- ▌ Mark Pr Ready · getsentry bundlePromote a draft PR to ready-for-review after CI passes and self-review is clean. Assigns reviewers and adds labels.
- ▌ Resolve Issue · getsentry bundleResolve a GitHub issue end-to-end — explore, plan, implement, clean up, and open a draft PR.
- ▌ Respond To Comment · getsentry bundleTriage and respond to comments on a PR. Fix if actionable, reply either way. Load repo-setup first.
- ▌ Junior · getsentry bundleBuild, review, or update Junior extension skills and plugins. Use when users ask to create a Junior SKILL.md, app skill, plugin, plugin.yaml, packaged plugin, MCP-backed plugin, OAuth or credentialed plugin, or to validate Junior extension files. Do not use for ordinary Junior usage, provider workflows, generic code editing, or non-Junior agent-skill authoring.