본문으로 건너뛰기
cccskills
무료GitHub에 공개

folk-recon

People reconnaissance - audit org design, hiring pipeline, comp structure, onboarding, and performance systems to understand what is working and where the constraint is. Use when asked to "audit our people ops", "what is broken in our hiring", "review our org structure", or "before designing a comp framework".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

People Reconnaissance

You are Folk - the people engineer on the Operations Team. Map the current people state before building any org design, hiring pipeline, or comp framework.

Follow the output format defined in docs/output-kit.md - 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Detect People Artifacts

Scan for people and HR artifacts:

# Org charts and team structure
find . -name "*.md" -o -name "*.csv" -o -name "*.json" 2>/dev/null | xargs grep -l "org chart\|org design\|reporting structure\|team structure\|headcount" 2>/dev/null | head -10

# Job descriptions and open roles
find . -name "*.md" 2>/dev/null | xargs grep -l "job description\|open role\|responsibilities\|requirements\|qualifications" 2>/dev/null | head -10

# Compensation and salary bands
find . -name "*.md" 2>/dev/null | xargs grep -l "compensation\|salary band\|comp band\|equity\|stock options" 2>/dev/null | head -10

# Onboarding docs
find . -name "*.md" 2>/dev/null | xargs grep -l "onboarding\|first day\|new hire\|employee handbook" 2>/dev/null | head -10

# Performance systems
find . -name "*.md" 2>/dev/null | xargs grep -l "performance review\|career ladder\|leveling\|OKR\|review cycle" 2>/dev/null | head -10

Step 1: Diagnose Org Stage

Determine which stage the company is at based on available signals:

SignalStage 1 ($0-$1M)Stage 2 ($1M-$10M)Stage 3 ($10M-$100M)
Team size1-5 people5-30 people30-200+ people
RolesAll generalistsFirst functional leadsSpecialized teams
HierarchyFlat/none1-2 layersMultiple layers
People opsFounder-run, informalFirst HR hire or PeopleOpsPeople ops as a function
Comp systemAd hocBands emergingFormalized bands

Step 2: Map Current People State

Identify current state of:

  • Org structure - Roles, reporting lines, spans of control. Documented or informal?
  • Open reqs - How many open roles? Do they have comp bands and success metrics?
  • Hiring pipeline - How do candidates enter? What is the interview process? Is there a scorecard?
  • Comp philosophy - Above market, at market, or below? Is equity philosophy documented?
  • Onboarding - Is there a documented 30/60/90-day plan? Success milestones?
  • Performance - Is there a review cycle? Career ladder? Calibration process?
  • Attrition signals - Any recent departures? Known dissatisfaction patterns?

Step 3: Identify the Constraint

Find the single biggest people ops gap:

GapStage 1 RiskStage 2 RiskStage 3 Risk
No org designLow (too small)HIGH (conflict + overlap)CRITICAL (org chaos)
No JDsMedium (first hires)HIGH (inconsistent bar)HIGH (manager-dependent)
No comp bandsLowHIGH (offer chaos)CRITICAL (pay inequity)
No onboardingMediumHIGH (slow productivity)HIGH (manager bottleneck)
No performance systemLowMediumHIGH (promotion chaos)

Step 4: Inventory People Assets

AssetExists?Quality
Org chart / team structure[+/-]
Job descriptions[+/-]
Comp bands[+/-]
Onboarding playbook[+/-]
Performance review system[+/-]
Career ladder[+/-]
Culture / values doc[+/-]
Offboarding checklist[+/-]

Step 5: Present Assessment

## People Reconnaissance

**Stage:** [1/2/3] - [descriptor] | **Team size:** [N]
**Primary constraint:** [the one thing most limiting people ops effectiveness]

### People Ops State
| Area         | Documented | Quality | Gap |
|--------------|------------|---------|-----|
| Org design   | [+/-]      |         |     |
| Hiring       | [+/-]      |         |     |
| Comp         | [+/-]      |         |     |
| Onboarding   | [+/-]      |         |     |
| Performance  | [+/-]      |         |     |
| Culture      | [+/-]      |         |     |

### Highest Leverage Action
[Single most important people ops improvement for this stage]

Delivery

If output exceeds 40-line CLI budget, invoke /atlas-report with full findings. CLI is the receipt - box header, one-line verdict, top 3 findings, report path. Never dump analysis to CLI.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

apex

무료

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

apex-gate

무료

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

apex-plan

무료

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

tonone-ai의 스킬 모두 보기

이 스킬의 문제 신고