Skills git-pr-workflows-onboard
๐Ÿ“ฆ

git-pr-workflows-onboard

Content revision r2 Safe โš™๏ธ External commands

Build Technical Onboarding Plans

Technical onboarding often lacks clear ownership, milestones, and role-specific guidance. This skill creates structured plans from pre-arrival preparation through 90-day progress reviews.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "git-pr-workflows-onboard" from https://skillstore.io/skills/sickn33-git-pr-workflows-onboard.md and its manifest at https://skillstore.io/api/skills/sickn33-git-pr-workflows-onboard/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "git-pr-workflows-onboard". Create a first-week plan for a mid-level backend engineer joining a hybrid payments team.

Expected outcome:

A daily plan covering access, security training, architecture orientation, local setup, pair programming, the first small pull request, and manager check-ins.

Using "git-pr-workflows-onboard". Prepare a 30-60-90 plan for a remote staff engineer.

Expected outcome:

  • First 30 days: map systems, stakeholders, risks, and team practices.
  • Days 31-60: lead a design review and propose prioritized improvements.
  • Days 61-90: own a technical initiative and establish measurable team outcomes.

Using "git-pr-workflows-onboard". Assess our onboarding process using time-to-productivity and feedback measures.

Expected outcome:

A measurement plan covering time to first commit, first deployment, milestone completion, knowledge retention, buddy feedback, and team integration.

Security Audit

Safe
v5 โ€ข 7/23/2026 Open versioned report

All 12 static findings are false positives caused by Markdown backticks or ordinary onboarding language. SKILL.md contains no executable commands, reconnaissance instructions, prompt injection, or data exfiltration intent. It only produces planning guidance and checklists.

1
Files scanned
425
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-git-pr-workflows-onboard/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-git-pr-workflows-onboard/security.svg)](https://skillstore.io/skills/sickn33-git-pr-workflows-onboard?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-git-pr-workflows-onboard?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-git-pr-workflows-onboard/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-git-pr-workflows-onboard.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). git-pr-workflows-onboard security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-git-pr-workflows-onboard/audits/5

BibTeX citation

@techreport{sickn33-sickn33-git-pr-workflows-onboard-2026, author = {sickn33}, title = {git-pr-workflows-onboard security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-git-pr-workflows-onboard/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "git-pr-workflows-onboard security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-git-pr-workflows-onboard/audits/5" identifiers: - type: other value: "skillstore:sickn33-git-pr-workflows-onboard:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Plan a Developer's First 90 Days

Create role-specific setup, learning, contribution, and review milestones for a new software engineer.

Coordinate Remote Onboarding

Build a distributed schedule covering equipment, access, communication norms, buddy meetings, and recorded learning sessions.

Accelerate a Senior Hire

Prepare architecture reviews, stakeholder meetings, technical assessments, and ownership milestones for an experienced engineering leader.

Try These Prompts

Create a Basic Onboarding Plan
Create a 30-day onboarding plan for a new [role] starting on [date]. Include preparation, Day 1, Week 1, and review milestones.
Plan Remote Engineer Onboarding
Build a 30-60-90 day plan for a remote [level] engineer in [time zone]. Cover access, communication, codebase learning, buddy support, and measurable outcomes.
Design an Accelerated Leadership Plan
Design an accelerated onboarding plan for a new [senior role]. Include architecture immersion, stakeholder mapping, process assessment, early decisions, and 30-day deliverables.
Improve an Existing Program
Review this onboarding program: [program details]. Identify coverage gaps, unclear ownership, unrealistic milestones, missing feedback loops, and useful success metrics. Produce a revised plan.

Best Practices

  • Provide role, seniority, location, start date, team structure, and technical requirements.
  • Review every milestone with the hiring manager, buddy, IT, security, and people operations.
  • Track progress through regular check-ins, measurable outcomes, and documented feedback.

Avoid

  • Do not reuse one plan without adapting it to the role, team, and location.
  • Do not place credentials, personal data, or confidential system details in prompts.
  • Do not treat checklist completion as proof of technical readiness or team integration.

Frequently Asked Questions

Can this skill create a complete 90-day plan?
Yes. It can organize preparation, first-day activities, weekly learning, contribution milestones, feedback, and 30-day, 60-day, and 90-day reviews.
Can it support remote or hybrid employees?
Yes. It covers equipment delivery, time zones, asynchronous communication, virtual meetings, recorded sessions, and remote feedback.
Does it configure accounts or development environments?
No. It creates planning guidance and checklists but cannot provision access, configure hardware, or execute setup commands.
What information produces the best plan?
Provide the role, seniority, start date, location, team structure, technical stack, access needs, and expected early outcomes.
Can it onboard senior engineering leaders?
Yes. It includes accelerated architecture immersion, stakeholder introductions, process assessment, technical planning, and early ownership milestones.
How should sensitive access information be handled?
Keep credentials and personal data out of prompts. Use approved identity, secrets management, IT, and security processes for actual access.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

8 downloads ยท 132 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all