Skip to content
Back to skills

Help

ASecurity

One-screen quick reference for the Wenlan plugin. Lists the daily verbs, the daily flow, where data lives, and how to view it without a GUI. Use when the user says "help", "what can I do", "list wenlan commands", "how do I use wenlan", invokes `/help`, or explicitly asks about import progress.

  • 79 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 12, 2026
ai-agentsdatabase

Works with

  • mcp

Security analysis

A100/100

Scanned October 12, 2026

npx -y skills add wenlan-app/wenlan --skill help --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Help?

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

Security grade badge for Help
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wenlan-app-help-wenlan/badge)](https://www.skillsdirectory.com/skills/wenlan-app-help-wenlan)

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: help
description: >
  One-screen quick reference for the Wenlan plugin. Lists the daily
  verbs, the daily flow, where data lives, and how to view it without a
  GUI. Use when the user says "help", "what can I do", "list wenlan
  commands", "how do I use wenlan", invokes `/help`, or explicitly asks
  about import progress.
allowed-tools: ["mcp__plugin_wenlan_wenlan__list_pending_imports"]
---

# /help

Print the Wenlan plugin reference card. The default help path is read-only and
never calls a tool.

## How to invoke

When triggered, output the block below verbatim. No editing, no
abbreviating, no embellishing. The user is asking for the menu. The one
exception: skip the `<!-- ... -->` comment lines inside the block; they mark
the generated verb list and are not part of the card.

```
Wenlan plugin — daily verbs

<!-- verbs:start -->
<!-- generated from plugin/skills/verbs.json by scripts/gen-plugin-verbs.mjs; do not edit -->
  /setup                       set up or repair Wenlan (installs the local runtime)
  /brief [topic]               load the Brief for the current Space (optional; not a boot step)
  /capture <x>                 save one durable memory in flow
  /recall <q>                  search local memory
  /lint [deep|repair] [scope]  diagnose, or resolve all findings safely
  /distill [t]                 synthesize or refresh source-backed pages for the active Space
  /pages [q]                   browse and open distilled pages
  /curate <surface>            deep audit of captures, revisions or refinements
  /forget <id>                 delete one memory by ID, after confirmation
  /handoff                     end-of-session debrief: captures, session log, Brief update
  /help                        one-screen quick reference
<!-- verbs:end -->

Import progress: ask explicitly; Wenlan checks `list_pending_imports` on demand.

Daily flow (~1 min overhead per session):

  1. start session  →  hook auto-checks runtime, silent if up
  2. /brief         →  resume a project or ask to catch up
  3. work normally  →  Claude proactively /captures durable facts
  4. /recall X      →  as needed for lookups
  5. /handoff       →  ~30 s, narrative session log + captures

Where your data lives (under ~/.wenlan/):

  ~/.wenlan/pages/      wiki pages distilled from your memories (md)
  ~/.wenlan/sessions/   session logs by date (md)
  ~/.wenlan/sessions/_status/  human receipts projected from Space Briefs

Memories and the graph live in a local database; location in docs/setup-and-data.md.

View it without a GUI:

  open ~/.wenlan/                  browse in Finder
  code ~/.wenlan/                  open in VS Code
  ln -s ~/.wenlan/pages ~/Vault/wenlan   # symlink into Obsidian for graph view

Three classes of artifact:
  - memories: granular, queryable, live in DB only (confirmed = stays in DB)
  - pages:    synthesized wikis, DB + ~/.wenlan/pages/*.md projection
  - sessions: chronological narrative, ~/.wenlan/sessions/*.md only

The local runtime must run at 127.0.0.1:7878. Hook prints "Wenlan is not running" and "/wenlan:setup" if down.

Models and keys do not enable background inference by themselves:
  wenlan steep status             show Everyday + Synthesis as off, ready, or paused
  wenlan steep configure --everyday <source> --synthesis <source>
                                  review the exact mapping, disclosure, and confirm
  wenlan steep disable            turn model-backed background work off
```

## Import progress (explicit only)

Only when the user explicitly asks whether an import/export is still running,
call `mcp__plugin_wenlan_wenlan__list_pending_imports`. Never call it during
ordinary `/help`, `/brief`, setup, or session-start flows.

## When to use

- User explicitly types `/help`.
- User asks "what can I do with wenlan", "list wenlan commands", "how
  does this plugin work", "remind me what verbs are available".
- First session after install — print this once on `/setup` success too.

## When NOT to use

- Specific factual lookup → use `/recall`.
- Setup troubleshooting → use `/setup` (it diagnoses + auto-installs).

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.