Skip to content
Back to skills

Lythoskill Project Onboarding

BSecurity

Session context loader. Reads the latest daily handoff to restore project context without redundant file exploration. Three-layer loading: CLAUDE.md (stable) → daily handoff (session state) → git verification (ground truth). Degrades to file exploration when no handoff exists. Read-side pair with project-scribe (scribe writes the daily, onboarding reads it).

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 18, 2026
ai-agentsrustgobashgitsecurity

Security analysis

B75/100
  • criticalAccesses system keychains or credential stores
  • criticalSends environment variables or credentials to an external URL

Pro scans all 5 files and shows the line behind each finding

Scanned October 18, 2026

npx -y skills add lythos-labs/lythoskill --skill lythoskill-project-onboarding --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lythoskill Project Onboarding?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lythoskill Project Onboarding
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/lythos-labs-lythoskill-project-onboarding/badge)](https://www.skillsdirectory.com/skills/lythos-labs-lythoskill-project-onboarding)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: lythoskill-project-onboarding
version: 0.20.1
description: |
  Session context loader. Reads the latest daily handoff to restore
  project context without redundant file exploration. Three-layer
  loading: CLAUDE.md (stable) → daily handoff (session state) →
  git verification (ground truth). Degrades to file exploration
  when no handoff exists. Read-side pair with project-scribe (scribe
  writes the daily, onboarding reads it).
when_to_use: |
  Start of session, resume work, onboard to project, review history,
  continue previous work, take over task, what happened last time,  先复盘 ("review first"), 了解项目 ("understand the project"), 接手任务 ("take over a task"), 继续之前的工作 ("continue previous work").
---

# Project Onboarding
> Read the handoff. Don't re-explore what's already written down.
## Three-Layer Loading
Loading order optimized for KV cache (stable content first, volatile last):
### Layer 1: Meta-skill (rarely changes)
```bash
cat CLAUDE.md
```

Provides: how to work in this project, architecture, conventions.
### Layer 2: Session State (from latest daily file)
```bash
# Find the most recent daily file
ls daily/*.md 2>/dev/null | sort | tail -1
# Read first section (## Session Handoff)
```

**Handoff is fresh if**: `git_commit` in handoff matches current HEAD and
date is recent (within 3 days).

**If fresh**: use handoff directly. Skip cortex/skills exploration.
**If stale or missing**: degrade to file exploration (see below).
**If stale + gap >7 days**: `git log --since="7 days ago" --oneline` to reconstruct activity, then `cortex probe` to check current state. Don't rely on stale Next Steps.

### Layer 3: Ground Truth Verification (always required)
```bash
git status
git log --oneline -5
```

Compare against handoff's **0. Verify Current State** section. If they diverge,
handoff is stale — flag it and rely on real-time git output.

### Layer 3b: CI 尾检 (always required)
```bash
export GH_TOKEN="$(security find-generic-password -s 'lythos-agent-pat' -w)"  # macOS
gh run list --workflow=CI --limit 1    # expect: the latest main push = success
```
CI is the one piece of ground truth git cannot show you. If the latest main
push is not `success`, triage it FIRST (per diagnosing-bugs) before starting
new work — red CI is a previous session's dropped ball, and it does not age
well (2026-10-13: three red pushes sat on main for ~6 hours because the
post-push check was skipped). `gh` 401 = token expired, tell the user.
## Degraded Exploration (no usable handoff)
Only when Layer 2 fails. Read in this order:
```bash
cat skill-deck.toml               # What skills are active
cat cortex/INDEX.md               # Project governance state
git log --oneline -10             # Recent changes
ls -lt cortex/adr/02-accepted/ | head -10   # Recent decisions
ls -lt cortex/wiki/02-research/ | head -10  # Recent research
ls cortex/epics/01-active/        # Active epics
ls cortex/tasks/01-backlog/       # Pending work
ls cortex/tasks/02-in-progress/   # Active work
```
**If the project has cortex**, the `ls -lt` on adr/, wiki/, epics/, tasks/ directories
tells you what happened recently without reading every file — timestamps reveal
the most recent decisions, research, and active work at a glance.

**Cortex ID = timestamp**: ADR-/TASK-/EPIC- prefixes use `yyyyMMddHHmmssSSS`.
This enables date-range grep reconstruction (e.g., `ls cortex/adr/02-accepted/ |
grep '^ADR-2026051'` finds all May 2026 decisions). Use this when a weekly is
missing or when verifying claims across a date range.
## Freshness Decision Table
| Condition | Verdict | Action |
|-----------|---------|--------|
| Daily exists, git_commit matches HEAD, date ≤3 days | ✅ Fresh | Use handoff directly |
| Daily exists, git_commit ≠ HEAD | ⚠️ Stale | Read handoff for context, but verify everything |
| Daily exists, date >3 days old | ⚠️ Probably stale | Same as above |
| No daily file found | ❌ Missing | Full degraded exploration |
## Output Format
After loading, summarize to user:
```
📋 Project: <name> (<tech stack>)
📌 Version: <tag> (git: <hash>)
📄 Source: daily/<date>.md | degraded exploration
⚠️ Pitfalls: <top 1-2 from handoff>
🎯 Current: <active task>
💡 Next: <prioritized next step>
✅ Verification: git state matches handoff | ⚠️ diverged
```
## Checklist
- [ ] Layer 1: Read CLAUDE.md
- [ ] Layer 2: Find latest daily/, read handoff section
- [ ] Assess freshness (git_commit match, date recency)
- [ ] Layer 3: Verify with `git status` + `git log`
- [ ] Layer 3b: CI 尾检 — `gh run list --workflow=CI --limit 1` is success; red → triage first
- [ ] If handoff fresh → use directly
- [ ] If handoff stale/missing → degraded exploration
- [ ] Output summary to user
## Gotchas
**Don't re-explore when handoff is fresh.** The whole point of the scribe→onboarding
pipeline is to avoid burning tokens on redundant `ls` and `cat`. If the handoff
exists and git state matches, trust it.

**Handoff date ≠ freshness.** A 2-day-old handoff with matching git_commit is
fresher than a same-day handoff whose git_commit doesn't match HEAD (someone
committed outside the agent session).
**Multiple handoff sections.** If the daily file has multiple `## Session Handoff`
sections (multiple sessions same day), read the **first** one — scribe prepends
new handoffs to the top of the file.
## Supporting References
| When you need to… | Read |
|--------------------|------|
| Understand the CQRS architecture with scribe | [references/cqrs-architecture.md](./references/cqrs-architecture.md) |
| See detailed output format variants and edge cases | [references/output-formats.md](./references/output-formats.md) |

Files in this skill

  • SKILL.md5.6 KB
  • references/autonomy-decision-quadrant.md2.4 KB
  • references/autonomy-quadrant-case-studies.md11.3 KB
  • references/cqrs-architecture.md1.5 KB
  • references/output-formats.md2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.