fix: update vendored skills to latest versions - #268
Open
pleaseai-release-bot[bot] wants to merge 1 commit into
Open
fix: update vendored skills to latest versions#268pleaseai-release-bot[bot] wants to merge 1 commit into
pleaseai-release-bot[bot] wants to merge 1 commit into
Conversation
pleaseai-release-bot
Bot
added
the
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
PR author is in the excluded authors list. |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 142 |
| Duplication | 16 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
🔍 Tessl Skill Review
|
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | The body is lean and assumes Claude's competence — no explanations of what GitHub is or how libraries work — with tight curl examples throughout. It drops to 4 rather than 5 only because the sheer volume of inline endpoint listings could be trimmed or externalized. |
| actionability | ████░ 4/5 | Most sections give copy-paste-ready curl commands with auth headers and JSON bodies, but several sections degrade to terse comment hints (e.g. "# Topics, languages, contributors, forks, collaborators, tags, transfer", "# Workflows: list, get, enable/disable, dispatch") rather than executable examples, leaving minor gaps. |
| workflow clarity | ███░░ 3/5 | The Common Patterns sections (OAuth flow, App installation token flow, create repo/issue/PR) are clearly sequenced, but destructive operations like DELETE /repos/... (which cascades issues and PRs) appear with no validation or verification step, capping this dimension at 3 per the destructive-operations guidance. |
| progressive disclosure | ███░░ 3/5 | The skill is a single ~600-line file with no bundle files and no external references; the full per-endpoint API reference is inlined in SKILL.md rather than split into reference files, matching the anchor where content that should be separate is inline despite reasonable section structure. |
Suggestions:
- Move the bulk of the per-endpoint API reference into a separate reference file (e.g. REFERENCE.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.
- Add an explicit validation/verification step before destructive calls such as
DELETE /repos/:owner/:repo(which cascades issues, PRs, and comments) — e.g. fetch the repo and confirm before deleting. - Expand the terse comment-only endpoint hints (e.g. "# Topics, languages, contributors, forks...", "# Workflows: list, get, enable/disable, dispatch") into concrete curl examples or link to where the full syntax lives.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | Lists multiple concrete actions — emulate repos/issues/PRs, set up OAuth flows, configure GitHub Apps, test webhooks, work with actions/checks — giving comprehensive coverage of the skill's capabilities. |
| completeness | █████ 5/5 | Explicitly answers both what ("Emulated GitHub REST API for local development and testing") and when ("Use when..." plus a dedicated "Triggers include" clause with concrete trigger phrases). |
| trigger term quality | █████ 5/5 | Provides comprehensive natural trigger terms including synonyms ("GitHub API", "emulate GitHub", "mock GitHub", "local GitHub") plus specific phrases like "test GitHub OAuth" and "GitHub App JWT" that users would naturally say. |
| distinctiveness conflict risk | █████ 5/5 | Occupies a clear niche (local GitHub API emulation) with distinct triggers unlikely to fire for unrelated skills; the "without hitting the real GitHub API" framing sharpens the boundary. |
plugins/emulate/.agents/skills/stripe/SKILL.md
The body is highly actionable and well-structured with executable code throughout, but it inlines a sizable API reference and omits validation checkpoints for destructive operations, capping workflow clarity.
Validation
⚠️ allowed_tools_field — 'allowed-tools' contains unusual tool name(s)
Full review details
Validation Checks
15/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | Assumes Claude's competence with no concept-explaining fluff and tight section headers, but the inline Next.js proxy block and full per-endpoint curl reference add some length that could be trimmed or externalized. |
| actionability | █████ 5/5 | Provides fully executable, copy-paste-ready guidance: start commands, SDK construction with real params, curl examples, and TypeScript webhook handler code covering the common cases. |
| workflow clarity | ███░░ 3/5 | Sections are sequenced by topic, but destructive operations (DELETE customer, cancel payment intent, expire checkout session) lack explicit validation checkpoints; the destructive-ops rule caps this at 3. |
| progressive disclosure | ████░ 4/5 | Well-organized into clear sections with no nested references, but the full API reference is inlined rather than split into a separate file, leaving minor organization gaps. |
Suggestions:
- Add explicit verification steps (e.g., retrieving the resource after DELETE, checking status before cancel/expire) before destructive curl calls to lift workflow_clarity above the destructive-op cap.
- Move the per-endpoint API reference into a separate REFERENCE.md and link to it one level deep to improve progressive_disclosure and conciseness.
- Externalize the Next.js adapter proxy block into an examples file to reduce inline length while keeping the core start/SDK guidance in SKILL.md.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | Lists multiple concrete actions ('process payments locally, test checkout flows, create customers, manage products and prices, handle payment intents, work with webhooks') with comprehensive coverage, matching the score-5 anchor. |
| completeness | █████ 5/5 | Explicitly answers what ('Emulated Stripe API for local development and testing') and when ('Use when the user needs...', with concrete trigger phrases), matching the score-5 anchor. |
| trigger term quality | █████ 5/5 | Comprehensive natural trigger phrases ('Stripe API', 'test payments locally', 'checkout flow', 'payment intent', 'Stripe webhook', 'Stripe SDK') plus the STRIPE_API_KEY env var, matching the score-5 anchor. |
| distinctiveness conflict risk | █████ 5/5 | Clear niche (local Stripe emulation) with distinct Stripe-specific triggers and minimal overlap risk with other skills. |
plugins/emulate/agent/skills/github/SKILL.md
Validation
⚠️ skill_md_line_count — SKILL.md is long (608 lines); consider splitting into references/ and linking- ❌ name_field — 'name' field is missing from frontmatter
Full review details
Validation Checks
14/16 checks passed.
plugins/emulate/agent/skills/stripe/SKILL.md
Validation
- ❌ name_field — 'name' field is missing from frontmatter
Full review details
Validation Checks
15/16 checks passed.
plugins/nuxt-ui/.agents/skills/nuxt-ui/SKILL.md
The body is a well-organized overview that balances concrete core rules and install snippets with progressive disclosure into reference files. It is lean and actionable, with only minor trimmable verbosity in the framework install sections.
Validation
⚠️ relative_links — Relative link issues: 13 deeper-than-1-level⚠️ referenced_paths_exist — Referenced path issues: 13 deeper-than-1-level
Full review details
Validation Checks
14/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | The body is dense and mostly lean — core rules, MCP tools, and a routing table each earn their tokens; the full multi-framework install blocks (Nuxt + Vue main.ts) could be trimmed or referenced but are justified. |
| actionability | ████░ 4/5 | Copy-paste-ready install config and concrete core rules (specific class names, slot file paths, override priority) give executable guidance; component-usage specifics are deferred to the MCP and references rather than inlined. |
| workflow clarity | ████░ 4/5 | A clear workflow is present via 'load relevant references before writing code' plus a task-to-reference routing table and numbered core rules; no destructive/batch validation loop is required for UI composition, so it is not capped. |
| progressive disclosure | █████ 5/5 | The body is a clean overview with well-signaled, one-level-deep references (guidelines, layouts, recipes, components) — all verified to exist — plus a routing table for easy navigation, matching the top anchor. |
Suggestions:
- Consider moving the full Vue (Vite) main.ts bootstrap into a reference file and keeping only the Nuxt quick-start inline, to tighten the install section.
- Add a one-line 'verify' cue after install (e.g., confirm
UAppwraps the app and@nuxt/uiresolves) to make the setup workflow self-checking. - Optionally surface a couple of inline component-usage snippets (e.g., a minimal Button/Input) so common cases are actionable without an MCP round-trip.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | ████░ 4/5 | Names the domain and several concrete actions ('customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces'); 'creating interfaces' is somewhat abstract, keeping it just below comprehensive. |
| completeness | █████ 5/5 | Explicitly answers 'what' ('Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming') and 'when' with a concrete 'Use when...' clause listing specific triggers, matching the top anchor. |
| trigger term quality | ████░ 4/5 | Includes natural phrases users would say ('building forms', 'customizing themes to match a brand', 'composing layouts like dashboards'), but lacks synonyms or file extensions like '.vue', so it is not fully comprehensive. |
| distinctiveness conflict risk | █████ 5/5 | Clear niche scoped to @nuxt/ui v4 and Vue components with distinct task triggers, giving minimal overlap risk with other skills. |
plugins/nuxt-ui/agent/skills/nuxt-ui/SKILL.md
Validation
- ❌ name_field — 'name' field is missing from frontmatter
⚠️ relative_links — Relative link issues: 13 deeper-than-1-level⚠️ referenced_paths_exist — Referenced path issues: 13 deeper-than-1-level
Full review details
Validation Checks
13/16 checks passed.
plugins/portless/.agents/skills/portless/SKILL.md
The body is highly actionable with concrete, executable commands and clear section organization, supported by strong troubleshooting and diagnostic guidance. Its main weakness is conciseness — several dense prose passages repeat or over-explain framework-specific behavior that could be condensed or moved to a reference file.
Full review details
Validation Checks
16/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ███░░ 3/5 | Mostly efficient with concrete commands, but several long prose passages re-explain mechanics Claude could infer (e.g. the multi-paragraph framework flag-injection rules in 'How It Works' and repeated TLD/hostname matching details), so it sits at the 'mostly efficient but could be tightened' anchor. |
| actionability | █████ 5/5 | Provides fully executable, copy-paste-ready commands throughout — install, run, monorepo config, turborepo scripts, env-var table, CLI reference — with specific examples covering common cases, matching the 5 anchor. |
| workflow clarity | ████░ 4/5 | Quick Start and Integration Patterns give a clear sequenced path with explicit validation/diagnostics via portless doctor and troubleshooting checkpoints; a few multi-step flows (proxy loop, Tailscale) lack an explicit validate-then-proceed loop, so it is just below the 5 anchor. |
| progressive disclosure | ████░ 4/5 | Well-organized with clear section headers and a single inlined reference structure (no bundle files, all content in SKILL.md); the CLI reference and env-var tables are appropriately placed, but with no external reference files the split could be marginally cleaner, placing it above the 3 anchor. |
Suggestions:
- Condense the framework flag-injection rules in 'How It Works' and 'Framework not respecting PORT' into a compact table or move the detailed exception list to a references file, since the same conditions are described twice.
- Tighten the multi-segment TLD/DNS-label rules paragraph in 'How It Works' to the essential constraints; the full per-label length rules read as reference material.
- Extract the long CLI Reference and Environment variables tables into a reference file and link to it from the body to improve progressive disclosure and reduce the body's token footprint.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | Names the tool and multiple concrete actions — 'Set up and use portless', 'configuring dev server names', 'setting up the local proxy', 'working with .localhost domains', 'troubleshooting port/proxy issues' — comprehensive coverage matching the 5 anchor. |
| completeness | █████ 5/5 | Explicitly states both what it does ('Set up and use portless for named local dev server URLs') and when to use it ('Use when integrating portless...configuring dev server names...troubleshooting port/proxy issues'), matching the 5 anchor with concrete trigger phrases. |
| trigger term quality | █████ 5/5 | Includes natural terms users say — 'named local dev server URLs', 'portless', 'dev server names', 'local proxy', '.localhost domains', 'port/proxy issues' — comprehensive coverage including synonyms and file extension. |
| distinctiveness conflict risk | █████ 5/5 | Has a clear niche — replacing port numbers with named .localhost URLs via a local proxy — with distinct triggers unlikely to fire for other skills, matching the 5 anchor. |
plugins/portless/agent/skills/portless/SKILL.md
Validation
- ❌ name_field — 'name' field is missing from frontmatter
Full review details
Validation Checks
15/16 checks passed.
plugins/react/.agents/skills/vercel-react-view-transitions/SKILL.md
A high-quality, dense reference for the React View Transition API with executable examples, well-organized progressive disclosure to four reference files, and clear conceptual sequencing. Minor room to tighten length and surface an explicit in-body validation checkpoint in the workflow.
Full review details
Validation Checks
16/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | Lean and information-dense with no padding of concepts Claude already knows, but at ~320 lines a few illustrative duplicate examples and explanatory clauses could be marginally trimmed, keeping it just below the fully-lean anchor. |
| actionability | █████ 5/5 | Provides copy-paste-ready JSX covering the common cases — enter/exit, list reorder, shared-element morph, Suspense reveal, and type-keyed directional navigation — with complete, executable snippets. |
| workflow clarity | ████░ 4/5 | Signals a clear implementation order ('Start with the audit — do not skip it', then copy CSS recipes) and delegates the detailed step sequence to implementation.md, but in-body validation checkpoints are only implied rather than explicit. |
| progressive disclosure | █████ 5/5 | Well-structured overview with one-level-deep, clearly signaled references to implementation.md, patterns.md, css-recipes.md, and nextjs.md (all present in references/), plus a consolidated Reference Files section for easy navigation. |
Suggestions:
- Tighten the body by collapsing illustrative duplicate examples (e.g., the two type-keyed enter/exit blocks) into one, reducing token load without losing coverage.
- Add one explicit validation checkpoint in the Implementation Workflow section (e.g., 'Verify the animation plays in Chromium 125+ and degrades silently on unsupported browsers') rather than delegating all checks to implementation.md.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | Lists multiple concrete actions — 'add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js' — giving comprehensive coverage of the API's capabilities. |
| completeness | █████ 5/5 | Explicitly answers both what ('Guide for implementing smooth, native-feeling animations using React's View Transition API') and when ('Use this skill whenever the user wants to...' plus 'Also use when the user mentions...') with concrete trigger phrases. |
| trigger term quality | █████ 5/5 | Comprehensive natural-term coverage including synonyms and technical identifiers: 'page transitions', 'route changes', 'shared element animations', 'list reorder', 'view transitions', 'startViewTransition', 'ViewTransition', 'transition types', and 'animating between UI states in React'. |
| distinctiveness conflict risk | █████ 5/5 | Occupies a clear niche (React View Transition API, no third-party animation libraries) with distinct, specific triggers and minimal overlap risk with other skills. |
plugins/react/agent/skills/vercel-react-view-transitions/SKILL.md
Validation
- ❌ name_field — 'name' field is missing from frontmatter
Full review details
Validation Checks
15/16 checks passed.
plugins/tiptap/.agents/skills/tiptap/SKILL.md
A well-structured overview that points into the cloned docs/source with concrete code for the headline collaboration case. Most feature sections are pointer-only, and a touch of intro padding and missing explicit verification keep it just below the top band.
Full review details
Validation Checks
16/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | Mostly lean and pointer-driven, assuming Claude's competence; the intro's "Do not guess or invent patterns, make sure the code you write matches the library source code and the documentation" is mildly redundant padding. |
| actionability | ████░ 4/5 | Gives executable commands ("npm view @tiptap/core version") and complete collaboration code (Y.Doc, Editor with Collaboration.configure, TiptapCollabProvider), though several feature sections only point to doc paths without code. |
| workflow clarity | ████░ 4/5 | Clear numbered sequences for setup and doc referencing plus a grounding self-check; no destructive/batch operations so the validation cap does not apply, but explicit verification checkpoints are otherwise light. |
| progressive disclosure | ████░ 4/5 | Well-organized into clear sections with one-level-deep references to specific tiptap-docs paths; no bundle files are present, and the structure is clean with minor organization gaps. |
Suggestions:
- Tighten the intro: collapse "Make sure any decision you make is in accordance to the 'Best Practices' section..." and "Do not guess or invent patterns..." into a single grounding instruction.
- Add a brief executable snippet or key API call for at least one more high-frequency feature (e.g. Comments or Import/Export) instead of only a doc-path pointer.
- Add an explicit verify step after implementing a feature (e.g. build/typecheck or run the editor against the docs example) to strengthen the workflow's feedback loop.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | Lists multiple concrete actions—"integrate and work with the Tiptap rich text editor", "building or modifying a rich text editor", "installing Tiptap extensions", and "implementing features like collaboration, comments, AI, or document conversion"—giving comprehensive coverage. |
| completeness | █████ 5/5 | Clearly states what it does and gives an explicit "Use when..." clause with concrete triggers (building/modifying, installing extensions, implementing listed features), matching the top anchor. |
| trigger term quality | ████░ 4/5 | Includes natural user phrases ("rich text editor with Tiptap", "installing Tiptap extensions", "collaboration, comments, AI", "document conversion") but is missing a few common synonyms; good but not exhaustive coverage. |
| distinctiveness conflict risk | █████ 5/5 | The Tiptap rich text editor niche is specific and the triggers are distinctive, so overlap with other skills is minimal. |
plugins/tiptap/agent/skills/tiptap/SKILL.md
Validation
- ❌ name_field — 'name' field is missing from frontmatter
Full review details
Validation Checks
15/16 checks passed.
plugins/turborepo/.agents/skills/turborepo/SKILL.md
The body is a high-quality, action-oriented overview: executable snippets, decision-tree routing, and a clean one-level reference index to a verified bundle. Its only weakness is mild repetition of the turbo run vs shorthand rule across several sections, which slightly dents conciseness.
Validation
⚠️ skill_md_line_count — SKILL.md is long (952 lines); consider splitting into references/ and linking⚠️ relative_links — Relative link issues: 24 deeper-than-1-level⚠️ referenced_paths_exist — Referenced path issues: 35 deeper-than-1-level
Full review details
Validation Checks
13/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | The body is mostly lean and assumes Claude's competence — code blocks are direct and concepts like transit nodes and package configurations are explained tersely with concrete examples rather than padded with basics. Some repetition (the turbo run vs turbo rule appears in three places) and a few restated rationales keep it just short of fully lean. |
| actionability | █████ 5/5 | Guidance is fully executable throughout: copy-paste-ready turbo.json and package.json snippets, exact CLI invocations (turbo run build --affected, TURBO_SCM_BASE=...), and decision trees that route each problem to a specific reference file or flag. Common cases are covered with concrete, specific examples. |
| workflow clarity | █████ 5/5 | Multi-step processes are clearly sequenced with explicit decision trees per scenario, and the 'Missing outputs' section even includes a verify-before-flag workflow (read the script, determine file output, only flag if files are cached). Error-recovery and conditional-fix guidance (declared vs undeclared dependencies) provides the feedback-loop quality the rubric rewards. |
| progressive disclosure | █████ 5/5 | The SKILL.md is a well-signaled overview with a full Reference Index table; all cited reference files exist (verified against the references/ bundle) and links are one level deep with clear purposes per file. Content is appropriately split — detailed topics live in references/ while the body stays navigable. |
Suggestions:
- Consolidate the 'turbo run vs turbo shorthand' guidance into a single authoritative section; it is currently restated in the Secondary Rule, the Anti-Patterns section, and the CI examples, which costs tokens for repeat readers.
- The 'Repetitive Task Configuration' and 'Overly Broad globalDependencies' sections both illustrate globalEnv/globalDependencies trade-offs; consider merging or cross-linking to reduce overlap.
- The frontmatter pins a canary version (2.10.11-canary.4) and the $schema URL references a canary build — surface this as a version-sensitive note so future maintainers know to refresh it.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | Names the domain and a comprehensive set of concrete capabilities — task pipelines, dependsOn, caching, remote cache, CLI flags (--filter, --affected), CI optimization, internal packages, boundaries — matching the 'multiple specific concrete actions; comprehensive coverage' anchor. |
| completeness | █████ 5/5 | Explicitly answers 'what' (build system guidance for pipelines/caching/etc.) and 'when' with a dedicated 'Triggers on:' list and a 'Use when user:' clause listing concrete scenarios, satisfying the highest anchor. |
| trigger term quality | █████ 5/5 | Covers natural user vocabulary including file names (turbo.json), config keys (dependsOn), CLI invocations ('turbo' CLI, --filter, --affected), and conceptual phrases (monorepo structure, CI optimization), giving comprehensive keyword coverage including synonyms. |
| distinctiveness conflict risk | █████ 5/5 | The Turborepo-specific triggers (turbo.json, dependsOn, the 'turbo' CLI, --filter, --affected) carve a clear niche with minimal overlap risk against other skills. |
plugins/turborepo/agent/skills/turborepo/SKILL.md
Validation
⚠️ skill_md_line_count — SKILL.md is long (942 lines); consider splitting into references/ and linking- ❌ name_field — 'name' field is missing from frontmatter
⚠️ relative_links — Relative link issues: 24 deeper-than-1-level⚠️ referenced_paths_exist — Referenced path issues: 35 deeper-than-1-level
Full review details
Validation Checks
12/16 checks passed.
plugins/vercel-sandbox/.agents/skills/sandbox/SKILL.md
The content is highly actionable with comprehensive executable examples and well-sequenced common patterns, but it is a monolithic wall of reference material inlined into SKILL.md rather than split across one-level-deep reference files, hurting token efficiency and progressive disclosure.
Validation
⚠️ skill_md_line_count — SKILL.md is long (1135 lines); consider splitting into references/ and linking
Full review details
Validation Checks
15/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ███░░ 3/5 | The body is mostly lean code examples with brief prose and avoids explaining concepts Claude already knows, but at ~1100 lines it inlines a large amount of API and CLI reference that competes for context budget; it could be tightened or split into reference files. |
| actionability | █████ 5/5 | Provides copy-paste-ready, executable TypeScript and bash/CLI examples covering creation, commands, files, network policy, snapshots, listing, auth, errors, and common patterns with concrete parameters. |
| workflow clarity | ████░ 4/5 | The Common Patterns section sequences multi-step workflows (dev server, build-and-test, base+fork, long-lived workspace) with validation checkpoints (e.g. if (install.exitCode !== 0) throw), but destructive operations like delete(), --rm, and snapshot rollback lack explicit validate/recovery feedback loops. |
| progressive disclosure | ██░░░ 2/5 | No references/scripts/assets bundle files exist; the entire SDK and CLI reference is inlined into a single ~1100-line SKILL.md, so content that clearly belongs in separate files (full API reference, CLI reference) is not split out, though section headers provide minimal navigation. |
Suggestions:
- Move the bulk of the API reference (Running Commands, File Operations, Network Policy, Snapshots, Listing) and the CLI Quick Reference into separate reference files (e.g. reference/api.md, reference/cli.md), keeping SKILL.md a concise overview that links to them one level deep.
- Add explicit validation/recovery feedback loops for destructive and batch operations — e.g. check sandbox state before
sandbox.delete(), confirm--rmintent, and verifycurrentSnapshotIdrollback succeeded. - Trim redundant inline duplication (e.g. sudo apt-get install examples appear in both Running Commands and System Packages) to reduce token cost.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | ████░ 4/5 | Names a concrete action ('Creates isolated Linux MicroVMs using Vercel Sandbox SDK') and several specific use cases (building code execution environments, running untrusted code, dev servers, testing in isolation), but the use cases read more as scenarios than an exhaustive capability list, so it falls just below the comprehensive anchor. |
| completeness | █████ 5/5 | Explicitly answers both 'what' (creates isolated Linux MicroVMs via Vercel Sandbox SDK) and 'when' ('Use when building code execution environments, running untrusted code... or when the user mentions...') with concrete trigger phrases. |
| trigger term quality | ████░ 4/5 | Includes natural terms users would say ('sandbox', 'microvm', 'isolated execution', '@vercel/sandbox') plus scenario phrasing, but a few common synonyms ('VM', 'containers', 'isolated environment') are absent, keeping it just under comprehensive. |
| distinctiveness conflict risk | █████ 5/5 | Targets a clear niche (Vercel Sandbox SDK / microvm) with distinct triggers and package mention, making conflict with unrelated skills minimal. |
plugins/vercel-sandbox/agent/skills/sandbox/SKILL.md
Validation
⚠️ skill_md_line_count — SKILL.md is long (1131 lines); consider splitting into references/ and linking- ❌ name_field — 'name' field is missing from frontmatter
Full review details
Validation Checks
14/16 checks passed.
To improve your score, point your agent at the Tessl optimization guide. Need help? Jump on our Discord.
Feedback
Report issues with this review at tesslio/skill-review, or send private feedback from your terminal with tessl feedback.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated refresh of vendored skills.sh skills to their latest upstream versions.
Updated lock directories:
plugins/emulateplugins/nuxt-uiplugins/portlessplugins/react-nativeplugins/reactplugins/slack-agentplugins/slidevplugins/tiptapplugins/tsdownplugins/turborepoplugins/vercel-sandboxplugins/web-designplugins/wordpressplugins/workflow-sdkGenerated by
.github/workflows/update-skills.yml→scripts/update-skills.ts.Summary by cubic
Refreshes all vendored
skills.shskills to their latest upstream versions. Adds a new Slack Agent skill and updates emulator behavior and MCP tool names that may require light client updates.Emulate
private_keyin seed; now you can omit it and read a generated RSA key viagithub.generatedSecrets(stable acrossgithub.reset()). CLI seed files still requireprivate_key.secret, responses now includeStripe-Signature: t=<timestamp>,v1=<signature>(HMAC SHA-256 over<timestamp>.<raw body>).Nuxt UI MCP tool names (breaking rename): snake_case → kebab-case. Update callers:
search_components→search-componentssearch_composables→search-composablessearch_icons→search-iconsget_component→get-componentget_component_metadata→get-component-metadatatsdown-migrateflags for non-interactive use: new--yes,--no-install, and--package-manager <name>. In CI, pass--yesand either--no-installor specify a package manager.Turborepo docs: version bump to 2.10.11-canary.4;
$schemaURLs updated. If your tooling validates JSON against the schema, point it to the new URL.React skills: view transitions guidance expanded (e.g.,
transitionTypesonnext/linkanduseRouter, CSS recipes, Next.js notes). Metadata files removed from some skills; no action required.New Slack Agent skill: adds comprehensive docs, patterns, references, and test templates under
plugins/slack-agent. No migration required.Minor doc/link/copy updates: Slidev link fix; Tiptap wording updates; lock files (
skills-lock.json) refreshed across plugins.Written for commit 87b2e33. Summary will update on new commits.