CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docs-onboard

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packs/nuxt/skills/docs-onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Create a quick summary of a module for onboarding.

Module: $ARGUMENTS

Steps

  1. Map the structure:
find modules/$ARGUMENTS -type f | head -40
find pages/ -path "*$ARGUMENTS*" -type f 2>/dev/null
find server/api/$ARGUMENTS -type f 2>/dev/null
  1. Summarize in quick format:

Endpoints

List the consumed endpoints (grep in services and server/api/).

Main Components

List components and their responsibilities (1 line each).

State

  • What is in useState? (simple shared state)
  • What is in Pinia? (complex client state)
  • What is in useAsyncData/useFetch? (server state)

Data Flow

Service ($fetch) -> Adapter (parse) -> Composable (useAsyncData) -> Component (UI)

Server API Routes

List Nitro routes in server/api/ (1 line each).

Points of Attention

  • Anything outside the ARCHITECTURE.md pattern?
  • Components > 200 lines?
  • Legacy code not yet migrated?
  • Explicit imports where auto-imports should work?
  1. Output: concise summary that a new developer can understand the module in 2 minutes.
Repository

fernandezbaptiste/specialist-agent

Path

packs/nuxt/skills/docs-onboard/SKILL.md

Revision

cd716d9

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill