Onboarding guides
Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.
npx -y skills add shinzoxD/knackbox --skill onboarding-guidesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 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.
What its author says it does
Copied from the file, not written here
Write new-hire and contributor onboarding guides that get people productive fast. Use whenever the user asks for an onboarding doc, starter guide for engineers, contributor getting-started, first-week plan, or "how do we onboard" handbook section.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, as published. Nobody here has run it
Onboarding Guides
Good onboarding reduces time-to-first-PR and time-to-first-decision. Short paths, owned checklists, and links to living systems — not a novel.
Structure
# Onboarding: <role or project>
## Day 0 access
- accounts, VPN, repos, secrets path
## First 48 hours
- setup script / dev environment
- run tests / app locally
- map of systems
## First week
- small good first issue / task
- who to ask (roles not only names if churny)
- rituals (standup, oncall, release)
## How we work
- code review norms, communication channels
## Glossary
…
## Checklist
- [ ] …
Rules
- Prefer commands that work copy-paste; mark OS differences.
- Link canonical docs; do not duplicate policies that drift.
- Separate employee onboarding from open-source contributor guides when needed.
- Security: never embed real secrets; describe where to obtain them.
- Include a "you are onboarded when…" definition.
- Keep under a readable length; progressive disclosure for deep topics.
Edge cases
- Remote / distributed: timezone and async norms.
- Contractors: access boundaries.
- OSS: CONTRIBUTING, DCO/CLA, issue labels.