Claude-skill-registry layton
Personal AI assistant for attention management. Use when user asks about focus, briefings, tracking items, or needs orientation across integrated skills.
git clone https://github.com/majiayu000/claude-skill-registry
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/layton" ~/.claude/skills/majiayu000-claude-skill-registry-layton && rm -rf "$T"
skills/data/layton/SKILL.mdStage 1 provides:
- Health checks (doctor)
- Temporal context
- Configuration management
- Skill inventory and discovery
- Workflow management
- AI orientation (combined status in one command) </objective>
<essential_principles>
- Use
directly for all state operations (never wrap it)bd - Always include
flag for machine-readable output--json - Always include
label on beads Layton createslayton - Only ONE bead should have
label at any timefocus - Workflows are AI instructions—Layton follows them, not executes them as code
- Skill files in
define how to query external tools.layton/skills/ - User workflows in
are customizable by users </essential_principles>.layton/workflows/
$LAYTON
Step 2: Menu
What would you like to do?
- Get oriented (full status check)
- Track something (add to attention list)
- Set focus (designate current work item)
- Retrospect on workflow (reflect on what worked)
- Something else
Wait for response before proceeding. </intake>
<routing> | Response | Workflow | | --- | --- | | 1, "orient", "status", "check" | Run `layton` CLI (no args) | | 2, "track", "watch", "monitor" | `workflows/track-item.md` | | 3, "focus", "working on" | `workflows/set-focus.md` | | 4, "retrospect", "reflect", "retro" | `workflows/retrospect.md` | | 5, other | Clarify intent, then select |Intent-based routing (bypass menu):
| Intent | Workflow |
|---|---|
| "setup", "configure", "onboard" | |
| "audit", "review instructions" | |
| "skill", "add skill", "create skill", "capture skill" | |
| "workflow", "add workflow", "create workflow", "capture workflow" | |
After selecting a workflow, read and follow it exactly. </routing>
<quick_start>
Get oriented (full status):
${CLAUDE_PLUGIN_ROOT}/scripts/layton
Setup for first-time users: Run workflow in
workflows/setup.md
Morning briefing: Follow
examples/morning-briefing.md (or create your own via layton workflows add morning-briefing)
Track something: Run workflow in
workflows/track-item.md
Set focus: Run workflow in
workflows/set-focus.md
Gather data from skills: Follow
examples/gather.md
Focus suggestions: Follow
examples/focus-suggestion.md
</quick_start>
<cli_commands>
Invocation: Set the LAYTON variable for this session:
LAYTON="${CLAUDE_PLUGIN_ROOT}/scripts/layton"
Orientation (no args):
$LAYTON
Returns combined doctor checks + skills inventory + workflows inventory. Use this for full AI orientation at start of any briefing or workflow.
Health check:
$LAYTON doctor
Temporal context:
$LAYTON context
Output: timestamp, time_of_day, day_of_week, work_hours, timezone
Configuration:
$LAYTON config show # Display config $LAYTON config init # Create default config $LAYTON config get <key> # Get specific value $LAYTON config set <key> <value> # Set value
Skills:
$LAYTON skills # List known skills from .layton/skills/ $LAYTON skills --discover # Find skills in skills/*/SKILL.md $LAYTON skills add <name> # Create new skill file from template
Workflows:
$LAYTON workflows # List workflows from .layton/workflows/ $LAYTON workflows add <name> # Create new workflow file from template
</cli_commands>
<workflows_index>
| Workflow | Purpose |
|---|---|
| setup.md | Interactive onboarding for new users |
| track-item.md | Add item to attention list |
| set-focus.md | Set current focus (only one at a time) |
| retrospect.md | Reflect on a completed workflow |
| audit-project-instructions.md | Review CLAUDE.md/AGENTS.md against best practices |
| author-skill.md | Create or capture a skill file |
| author-workflow.md | Create or capture a workflow file |
</workflows_index>
<reference_index>
| Reference | Content |
|---|---|
| persona.md | Layton's voice and persona characteristics |
| beads-commands.md | bd CLI command reference for state operations |
| project-instructions.md | Best practices for CLAUDE.md/AGENTS.md files |
| skill-authoring.md | Template and guide for writing skill files |
| workflow-authoring.md | Template and guide for writing workflow files |
</reference_index>
<examples_index> Example Workflows (in
examples/):
- Context-aware daily briefingmorning-briefing.md
- Aggregate data from all skillsgather.md
- Help user decide what to work onfocus-suggestion.md
To use an example:
- Study it in
for patternsexamples/ - Create user version:
layton workflows add <name> - Customize in
</examples_index>.layton/workflows/
<skill_integration>
Layton integrates with external skills through "skill files" in
.layton/skills/.
Discovery:
$LAYTON skills --discover
Shows skills available in
skills/*/SKILL.md that can be integrated.
Adding a skill:
$LAYTON skills add gtd
Creates
.layton/skills/gtd.md from template. Edit to document:
- Commands to run when gathering data
- What information to extract from output
- Key metrics to surface in briefings
Using skill files: When following workflows like
gather.md or morning-briefing.md, read each skill file in .layton/skills/ and execute its documented commands.
</skill_integration>
<success_criteria>
- User knows what they're tracking (bd list --label watching)
- User knows their current focus (bd list --label focus)
- Briefings adapt to time of day and workload
- Skills are discovered and integrated via skill files
- User can customize workflows in .layton/workflows/
- Orientation command provides full status in one call </success_criteria>