AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Logseq Inbox Triage

skill-weilong-qin-logseq-skills-logseq-inbox-triage · by Weilong-Qin

Help a user empty their [[inbox]] page in a Logseq file graph. Provide a repeatable triage flow, rewrite items into tasks/notes, and preserve metadata child blocks.

No reviews yet
0 installs
41 views
0.0% view→install

Install

$ agentstack add skill-weilong-qin-logseq-skills-logseq-inbox-triage

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-weilong-qin-logseq-skills-logseq-inbox-triage)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
8mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Logseq Inbox Triage? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Logseq Inbox Triage (File Graph)

This skill guides a user through processing and emptying a dedicated [[inbox]] page in a Logseq file graph.

It assumes captured items look like:

  • A main bullet that ends with #inbox
  • Child blocks containing metadata (captured-at::, source::, etc.)

Goal

  • [[inbox]] becomes close to empty (or only contains genuinely unprocessed items).
  • Every remaining commitment has a clear home: a project page, a context list, a calendar/deadline, or a someday list.

Triage Rules (Decision Tree)

Process items top-to-bottom. For each item, choose exactly one outcome.

0) Trash

If it is irrelevant, duplicate, or no longer useful:

  • Delete it.

1) Do now (2-minute rule)

If it takes ~2 minutes or less:

  • Do it immediately.
  • Mark the block DONE (or delete it) and keep a brief completion note if useful.

2) Clarify

If the item is vague (no clear action):

  • Rewrite the main line into a clear next action, or
  • Add a child block next-action:: ... and leave the main line as a note.

3) Next action (single-step)

If it is actionable and not blocked:

  • Convert the main line to a task marker (TODO is the default).
  • Add context/project metadata if known.
  • Move the block out of [[inbox]] into the appropriate page:
  • [[Projects/]] for project-related work
  • [[@phone]], [[@computer]], [[@errands]] (or your context pages)
  • a dedicated list page like [[Next Actions]]

Important:

  • Remove #inbox from the main line after moving.

4) Project

If it requires multiple steps:

  • Create/identify a project page.
  • Move the item there as the project header or first note.
  • Add at least one child task under it as a concrete next action.
  • Remove #inbox.

5) Waiting for

If someone else must act first:

  • Use WAIT / WAITING marker (or keep TODO but add waiting metadata).
  • Add waiting-for:: [[Person]] if known.
  • Move to [[Waiting For]] or a person/project page.
  • Remove #inbox.

6) Schedule / Deadline

If it must happen on/after a specific date:

  • Keep it as a task (TODO).
  • Add Logseq’s scheduling syntax via /Scheduled or /Deadline.
  • Optionally add context/project.
  • Move it to the relevant project page.
  • Remove #inbox.

7) Someday / Reference

If it is not actionable now:

  • Move it to [[Someday]] or a topic page.
  • Keep it as a note (no task marker) unless you intentionally want it tracked.
  • Remove #inbox.

Rewrite Guidelines

Preserve metadata child blocks

Keep:

  • captured-at:: [[Today]] (or the captured date)
  • source:: ...

Add when useful:

  • project:: [[...]]
  • area:: [[...]]
  • context:: [[...]]
  • waiting-for:: [[...]]

Remove inbox marker when processed

  • Only unprocessed items should still end with #inbox.
  • Everything processed should have #inbox removed.

Examples

Convert to next action

Before:

- Email Alice #inbox
	- captured-at:: [[Today]]
	- source:: phone

After (moved to a project page or Next Actions page):

- TODO Email Alice about contract terms
	- captured-at:: [[Today]]
	- source:: phone
	- context:: [[@computer]]

Convert to project

- Project: Plan Q1 offsite
	- captured-at:: [[Today]]
	- source:: meeting
	- TODO Draft agenda
		- context:: [[@computer]]
	- TODO Confirm attendees
		- context:: [[@phone]]

Quality Checklist

  • [ ] Every unprocessed item still ends with #inbox
  • [ ] Every processed item has #inbox removed
  • [ ] Tasks use file-graph markers (TODO/DOING/DONE/WAIT/...)
  • [ ] Metadata child blocks are preserved
  • [ ] Projects have at least one explicit next action

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.