fix: update vendored skills to latest versions#209
Conversation
pleaseai-bot
Bot
added
the
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🔍 Tessl Skill Review
|
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ██░ 2/3 | The skill is mostly efficient but includes some unnecessary content. The long list of doc file paths is useful as a reference but could be more compact. The 'Core concepts' section explains things Claude likely already understands from the type definitions. The guides/templates section is quite lengthy. However, it avoids explaining basic concepts like what a chat bot is. |
| actionability | ███ 3/3 | The skill provides fully executable TypeScript code examples for the quick start, streaming with AI SDK, and JSX cards. The webhook setup, event handler table, and adapter catalog usage are all concrete and specific. File paths to read for detailed guidance are explicit and actionable. |
| workflow clarity | ██░ 2/3 | The skill provides a clear quick start flow and event handler table, but lacks explicit validation checkpoints. There's no 'verify your bot is working' step, no error handling guidance, and no feedback loop for common setup issues. The workflow for building a custom adapter lists docs to read but doesn't sequence the actual steps with validation. |
| progressive disclosure | ███ 3/3 | Excellent progressive disclosure structure. The SKILL.md serves as a clear overview with well-signaled one-level-deep references to specific doc files in node_modules. Content is appropriately split between the overview (quick start, core concepts, event handlers) and detailed docs (handling-events.mdx, actions.mdx, etc.). Navigation is clear with explicit file paths. |
Overall: This is a well-structured skill that serves effectively as a reference hub for the Chat SDK. Its greatest strength is progressive disclosure — it provides a concise overview with clear pointers to detailed documentation. The actionability is strong with executable code examples. The main weaknesses are some verbosity in the resource listings and missing validation/verification steps in the workflows.
Suggestions:
- Add a brief verification step after the quick start code (e.g., 'Send a test message to confirm the bot responds') to improve workflow clarity.
- Condense the guides section — consider listing just the file paths with one-line descriptions rather than full paragraph descriptions to improve conciseness.
plugins/portless/.agents/skills/portless/SKILL.md
Review Details
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | █░░ 1/3 | Extremely verbose at ~400+ lines. Includes extensive motivational 'Why portless' section explaining problems Claude already understands, exhaustive environment variable tables, full CLI reference tables, and detailed troubleshooting for every edge case. Much of this content (LAN mode details, Tailscale/ngrok setup, mDNS helpers, OS service installation) could be split into reference files. The 'Why portless' section alone is pure padding. |
| actionability | ███ 3/3 | Highly actionable with concrete, copy-paste-ready commands throughout. Installation commands, Quick Start examples, integration patterns with real JSON configs, CLI commands with expected outputs, and troubleshooting steps all provide specific executable guidance. |
| workflow clarity | ██░ 2/3 | The Quick Start provides a clear sequence, and integration patterns show concrete steps. However, there are no explicit validation checkpoints — for example, after proxy start there's no 'verify it's running' step, and the monorepo setup doesn't include verification that all services registered correctly. The troubleshooting section partially compensates but is reactive rather than proactive. |
| progressive disclosure | █░░ 1/3 | Monolithic wall of text with no references to external files. Everything — CLI reference, environment variables, LAN mode details, Tailscale/ngrok integration, OS service setup, troubleshooting — is inlined in a single massive document. The CLI reference table alone could be a separate file. No bundle files exist to offload content to, but the skill doesn't even suggest or structure content for separation. |
Overall: The skill is highly actionable with excellent concrete examples and commands, but severely undermined by its length and lack of structure. It reads more like complete product documentation than a focused skill file — the 'Why portless' motivation section, exhaustive CLI reference, environment variable table, and detailed coverage of every feature (LAN, Tailscale, ngrok, OS services) make it far too verbose for a context-window-conscious skill. The content would benefit enormously from splitting into a concise overview with references to detailed sub-files.
Suggestions:
- Remove the entire 'Why portless' section — Claude doesn't need motivation to use a tool it's been instructed to use.
- Extract the CLI Reference table, Environment Variables table, and detailed feature sections (LAN mode, Tailscale, ngrok, OS service) into separate referenced files (e.g., CLI_REFERENCE.md, ADVANCED_FEATURES.md).
- Keep SKILL.md focused on: Installation, Quick Start, the most common integration pattern (zero-config), and a brief troubleshooting section with only the top 2-3 issues.
- Add explicit validation steps after key operations, e.g., 'Run
portless listto verify your app is registered' after starting an app through the proxy.
plugins/prisma/.agents/skills/prisma-cli/SKILL.md
Review Details
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ██░ 2/3 | The skill is mostly efficient with good use of tables and code blocks, but includes some redundancy — the 'Rule Categories by Priority' table adds little value, the 'When to Apply' section restates what's obvious from the command list, and the 'Command Categories' table partially duplicates the Quick Reference section. The boundary note is useful but could be shorter. |
| actionability | ███ 3/3 | Every command is shown with fully executable bash examples and concrete flags. The prisma.config.ts configuration example is complete and copy-paste ready. Code blocks cover all major workflows from init through migrations to studio. |
| workflow clarity | ██░ 2/3 | While individual commands are well-documented, the main SKILL.md lacks explicit multi-step workflow sequences with validation checkpoints. For example, the migration workflow doesn't include a 'check status before deploying' step or error recovery loops. The reference files (like migrate-deploy.md) do include better workflow guidance, but the main skill body presents commands more as a flat reference than a guided workflow. |
| progressive disclosure | ███ 3/3 | Excellent structure: the main SKILL.md provides a concise quick reference overview, then clearly lists all 18 reference files with descriptive labels. References are one level deep, well-organized by command category, and all referenced paths match the actual bundle file listing exactly. |
Overall: This is a well-structured CLI reference skill with strong actionability and excellent progressive disclosure across its bundle of reference files. The main weaknesses are moderate verbosity from redundant organizational tables and a lack of explicit multi-step workflow sequences with validation checkpoints in the main body. The reference files themselves are thorough and well-written.
Suggestions:
- Remove or consolidate the 'Rule Categories by Priority' table and 'When to Apply' section, which add little value beyond what the Command Categories table and Quick Reference already convey.
- Add a brief 'Common Workflows' section with explicit step sequences including validation checkpoints, e.g., 'Development workflow: 1. prisma migrate dev → 2. prisma generate → 3. prisma db seed → 4. prisma studio to verify'.
plugins/workflow/.agents/skills/workflow/SKILL.md
Review Details
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ██░ 2/3 | The skill is mostly efficient and provides genuinely useful information Claude wouldn't know (SDK-specific directives, sandbox limitations, API signatures). However, some sections are verbose — the namespaced streams example is overly long, the serialization section could be tighter, and there's some redundancy (error handling appears twice). The streaming examples repeat the try/finally writer pattern excessively. |
| actionability | ███ 3/3 | Excellent actionability throughout — nearly every section includes fully executable TypeScript code examples with correct imports, concrete CLI commands for debugging, and specific API signatures with parameter details. The code is copy-paste ready and covers the full range of SDK usage patterns. |
| workflow clarity | ███ 3/3 | Multi-step processes are clearly sequenced with explicit validation guidance. The testing section shows clear step-by-step patterns (start → waitForHook → resumeHook → wakeUp → check returnValue). The document discovery workflow at the top (find docs → search content) is clear. Sandbox limitations have explicit workarounds. The serde section includes validation tools and compliance checking steps. |
| progressive disclosure | ██░ 2/3 | The skill effectively references bundled documentation in node_modules for deeper exploration (docs directory structure, specific .mdx files). However, the SKILL.md itself is quite long (~500+ lines) and includes extensive inline content (namespaced streams, full observability API, serde details) that could be split into separate reference files. Without bundle files to offload to, the monolithic structure is somewhat justified but still heavy. |
Overall: This is a strong, highly actionable skill that provides comprehensive coverage of the Workflow SDK with executable code examples and clear API references. Its main weakness is length — several sections (namespaced streams, serialization/serde, observability) are quite detailed and could benefit from being split into separate reference files to keep the main SKILL.md as a concise overview. The workflow clarity is excellent with good validation steps and debugging tools clearly documented.
Suggestions:
- Extract the detailed Observability/World SDK section, Serialization/Serde section, and Streaming/Namespaced Streams section into separate reference files, keeping only brief summaries with links in the main SKILL.md
- Remove the duplicate error handling content — it appears both as a standalone section and again as 'Error Handling Patterns' at the end with overlapping examples
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.
Up to standards ✅🟢 Issues
|
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull Request Overview
This PR performs an automated update of documentation and system instructions for various AI skills. While the changes are generally up to standards according to automated quality checks, there is a significant syntax error in the Workflow documentation that provides an invalid code example for 'world.runs.list'. This could cause errors if utilized by developers or AI agents. Additionally, there are minor inconsistencies in the Portless CLI documentation and incomplete examples in the Nuxt UI guidelines. The update fulfills most acceptance criteria, though verification scenarios for new ngrok flags and Prisma CLI boundaries are currently missing.
1 comment outside of the diff
plugins/workflow/.agents/skills/workflow/SKILL.md
line 641🟡 MEDIUM RISK
Replace the type union notation with a concrete value to provide valid code examples.const { data, cursor } = await world.runs.list({ pagination: { cursor }, resolveData: 'all' });
Test suggestions
- Verify Portless CLI documentation includes the new --ngrok flag and PORTLESS_NGROK environment variable
- Verify Workflow skill version is incremented to 1.9 and documentation paths are updated
- Confirm Nuxt UI design system guidelines include the 'Replace instead of merge' function pattern for slots
- Ensure Prisma CLI description explicitly directs users to the prisma-compute skill for app deployment tasks
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify Portless CLI documentation includes the new --ngrok flag and PORTLESS_NGROK environment variable
2. Verify Workflow skill version is incremented to 1.9 and documentation paths are updated
3. Confirm Nuxt UI design system guidelines include the 'Replace instead of merge' function pattern for slots
4. Ensure Prisma CLI description explicitly directs users to the prisma-compute skill for app deployment tasks
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
|
1 participant
Automated refresh of vendored skills.sh skills to their latest upstream versions.
Updated lock directories:
plugins/chat-sdkplugins/nuxt-uiplugins/portlessplugins/prismaplugins/tsdownplugins/workflowGenerated by
.github/workflows/update-skills.yml→scripts/update-skills.ts.Summary by cubic
Refreshes vendored
skills.shcontent to the latest upstream across plugins. Adds Better Auth and Mastra skills, updates docs forchat,nuxt/ui,portless, Prisma CLI,tsdown, andworkflow, and updates lockfiles.--ngrok,PORTLESS_NGROK,PORTLESS_LAN_IP, and service install flags (--lan,--wildcard,--state-dir); docs updated for CLI and requirements.chat/adaptersstatic catalog and fixes the state docs path.prisma-computefor@prisma/cli app deployand related), and removespublicPathfrom the WASM recipe.Written for commit a751ba4. Summary will update on new commits.