help

Design Community

Skill notes

When to Activate

User says: "help", "what should I work on?" When stuck or unsure Returning after time away Multiple things competing for attention

1. Deep Context Check

Git status: Inbox: Decisions pending: Schema/summary:

3. Suggest Priorities

If uncommitted changes: If inbox has items: If pending decisions: If everything clean:

Difference from Start/Startup

start/startup: Quick context, begin work help: Deep analysis, identify problems, suggest priorities Use help when stuck or returning after time away.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@majiayu000 · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Help (System Assessment)

Deep assessment of workspace state. Identifies blockers, suggests priorities.

## When to Activate

- User says: "help", "what should I work on?"
- When stuck or unsure
- Returning after time away
- Multiple things competing for attention

## Process

### 1. Deep Context Check

**Git status:**
```bash
git status -sb
git log --oneline -5
git diff --stat
```

**Inbox:**
```bash
ls -lt inbox/session-summaries/*.md 2>/dev/null | head -5
ls inbox/ 2>/dev/null
```

**Decisions pending:**
```bash
ls decisions/*.md 2>/dev/null | head -10
```

**Schema/summary:**
```bash
cat .claude/tachikoma-summary.yaml 2>/dev/null
```

### 2. Report Findings

```
System Assessment (YYYY-MM-DD):

Git Status:
- Branch: [name]
- Uncommitted changes: [yes/no]
- Recent commits: [summary]

Inbox Status:
- Session summaries: [N files]
- Status: [Clean / Needs processing]

Pending Decisions:
- [N] decisions waiting for review
- [List key ones]

Tachikoma Summary:
- Last scan: [date]
- Observations: [key points]
```

### 3. Suggest Priorities

**If uncommitted changes:**
```
Priority 1: Git hygiene
- Uncommitted changes in [files]
- Review and commit before other work
```

**If inbox has items:**
```
Priority 1: Process inbox
- [N] session summaries from [dates]
- Run "learn" to update system
- Then "cleanup" to archive
```

**If pending decisions:**
```
Priority 1: Review decisions
- [N] tachikoma decisions pending
- Review and apply or reject
```

**If everything clean:**
```
System is healthy:
- Inbox clean
- Git clean
- No pending decisions

What do you want to work on?
```

### 4. Ask What User Wants

```
Based on this, what do you want to focus on?
```

## Difference from Start/Startup

- **start/startup:** Quick context, begin work
- **help:** Deep analysis, identify problems, suggest priorities

Use `help` when stuck or returning after time away.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.