pages

Featured

Browse, open, or print distilled pages, reusing the `wenlan pages` CLI for the actual open (one implementation on your PATH, no setup). `/wenlan pages <query>` opens the page when one matches, or shows a small native picker when 2-4 match. `/wenlan pages <query> --print` reads the page here instead of opening an editor. `/wenlan pages` lists recent pages. Invoked as `/wenlan pages [query] [--print]`.

AI & Automation 498 stars 8 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 97/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /wenlan pages Open a distilled page fast. The **`wenlan pages`** CLI does the open (one local command on your PATH — nothing to register, source, or install). This skill only adds a small native picker for the ambiguous case. **Do not read a page body unless the user asks to see it here. Never render a metadata card.** By default resolve by title / filename only — the file opens in your editor, which renders and searches it better than chat. Keeping bodies out is what keeps this cheap. The one exception is `--print` below. Resolve the binary once (the agent shell's PATH may omit `~/.wenlan/bin`): ```bash W="$(command -v wenlan || echo "$HOME/.wenlan/bin/wenlan")" ``` ## `/wenlan pages <query>` — open, or pick when ambiguous Run ONE Bash block **with the command sandbox DISABLED** (opening calls the OS launcher `open`/`xdg-open`, which a sandboxed shell can't reach, and would else fail with `kLSUnknownErr`): ```bash W="$(command -v wenlan || echo "$HOME/.wenlan/bin/wenlan")" "$W" pages "<query>" ``` Act on its output — do NOT re-fetch, list again, or read bodies: - **`Opened <path>`** → one page matched and is now open. Print that line. Done. - **`no page matches: …`** → print it; suggest `/wenlan steep <query>`. - **`N matches for … `** followed by `title · filename` lines → several matched: - **2-4 matches** → present them with `AskUserQuestion`, one option each: **label** = title, **description** = filename (titles can repeat, so the filename is the rea...

Details

Author
wenlan-app
Repository
wenlan-app/wenlan
Created
7 months ago
Last Updated
today
Language
Rust
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

pages

Browse or open distilled pages, reusing the `wenlan pages` CLI for the actual open (one implementation on your PATH, no setup). `/pages <query>` opens the page when one matches, or shows a small native picker when 2-4 match. `/pages` lists recent pages. Invoked as `/pages [query]`.

498 Updated today
7xuanlu
AI & Automation Solid

wenlan

The one front door to Wenlan. Takes plain words after `/wenlan` and runs the right Wenlan workflow; bare `/wenlan` shows status or starts setup. Use for: setting up or fixing Wenlan ("set up wenlan", "is wenlan working", "裝好了嗎"), turning what was imported or saved into notes and bringing out of date notes up to date ("steep", "沉澱", "整理成筆記"), getting to know a code repository ("build a wiki for this repo", "認識這個倉庫"), opening or listing notes ("open my note on X", "打開筆記"), organizing existing pages and folders ("organize my notes", "整理我的資料"), checking memory quality or cleaning up ("lint", "檢查重複", "清一清"), reviewing pending items ("review what's waiting", "看待確認的"), deleting one memory ("forget <id>", "刪掉這筆"), and changing how the app looks ("make Wenlan purple", "換個主題"). Say what to prepare, update, or rearrange; these all use steep. Invoked as `/wenlan [what you want]`.

498 Updated today
wenlan-app
Data & Documents Listed

pages

ALWAYS start here when the user wants a page OR a doc: page, living page, doc, document, living doc, bongo or bongo doc (the old name; new ones are made here, not by a Bongo connector), shared or collaborative doc, write-up, one-pager, memo, brief, proposal, plan, spec, report, meeting notes, notes, checklist, tracker, or anything to read, edit, comment on and share together — 'write this up', 'put this in a doc', 'draft a brief', 'jot this down somewhere we can share and edit', 'turn this file into a page' — the DEFAULT for any of these when no file format is named; a Word/.docx, PDF, .pptx or .xlsx FILE asked for by name goes to that format's skill instead. Also whenever the pages connector is about to be used to create a page. Not for READMEs, code or docstrings. A lowercase /pages as its own word anywhere in the message (not in a URL, path or longer name) invokes this skill whatever else is asked — a summary, an answer, a comparison, a plan: the page is the reply.

101 Updated 2 months ago
Razshy