agentsclimarketplace

Onboarding

Skill ulises-jeremias/agent-toolkit/skills/core/onboarding

Getting started guide for new users. Walks through setup validation, the skill/agent hierarchy, and the three most useful commands per role (developer, PM, tech lead). Use when someone is new to the workstation or asks "where do I start?"From its SKILL.md

Install
npx -y skills add ulises-jeremias/agent-toolkit --skill onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, as published. Nobody here has run it

Onboarding

Welcome to . This skill guides new users through initial setup and daily usage.

When to use

  • User asks "where do I start?" or "how does this work?"
  • First-time setup after chezmoi apply
  • Troubleshooting a broken installation
  • Onboarding a teammate

Step 1 — Validate setup

doctor

Expected: result: COMPLIANT. If any check fails, doctor shows the fix command.

For persistent issues:

update-check            # check for available updates
skills list             # verify skills are installed
skills sync             # re-sync symlinks to AI tools

Step 2 — Understand the hierarchy

User message
    ↓
Orchestrator (assistant)
    ↓ routes to
Workflow skill (WHAT — decides scope and gates)
    e.g. workflow-generic-project
    ↓ delegates to
Tool skill (HOW — executes CLI commands)
    e.g. clickup-cli, github-cli-workflow

Skills are invoked via the skill tool (e.g. /planning). Agents are invoked via @mention (e.g. @planner). Never use the skill tool for agents.

Step 3 — First commands by role

Developer

# Start any task
/workflow-generic-project

# After code changes — review before PR
@code-reviewer

# CI failing
/gh-fix-ci

Product Manager / Tech Lead

# Plan a feature
@planner

# Create a ClickUp task
/clickup-cli  # then: clickup task create --current --name "..."

# Project health check
/project-assessment

Anyone

# Check workstation health
doctor

# Find which skill to use
# → ask the orchestrator: "what skill should I use for X?"

# Load client/project context
agent-toolkit workspace load packs/<client>.yaml   # canonical; harness alias: ./bin/workspace-context load

Key concepts in 60 seconds

ConceptWhat it means
PackContext bundle for a client/project (repos, constraints, commands)
SkillReusable AI prompt for a specific task (WHAT or HOW)
AgentSpecialized AI persona with restricted tool access (invoked via @mention)
LoopRecurring autonomous process with state, tiers, and cost budgets
L1 / L2 / L3Loop autonomy tiers: L1=observe-only, L2=PR-gated, L3=unattended
knowledge/Persistent memory across sessions

Anti-patterns

  • Do not skip doctor — it catches 90% of setup issues
  • Do not invoke agents via the skill tool — use @mention
  • Do not run L3 loops without 3+ clean L1 runs first

Next steps

  • Load a project pack: agent-toolkit workspace load packs/<project>.yaml (harness alias: ./bin/workspace-context)
  • Run your first task: /workflow-generic-project
  • Set up daily loop: agent-toolkit loop init daily-triage

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.