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

Act

skill-markfive-proto-obsidian-brain-vault-act · by markfive-proto

Turn thinking into doing with Obsidian vaults. Get focused next actions, make decisions using your own notes, or promote buried ideas into standalone notes. Use when the user has ideas but needs help prioritizing, deciding, or organizing for action.

— No reviews yet
0 installs
38 views
0.0% view→install

Install

$ agentstack add skill-markfive-proto-obsidian-brain-vault-act

✓ 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-markfive-proto-obsidian-brain-vault-act)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo 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 Act? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Act Pack — "I have 100 ideas and no plan"

Tools for turning vault knowledge into decisions and actions.

Commands

/next — What should I focus on right now?

When the user invokes /next:

  1. Gather current state:
  • obs tasks pending --json — open tasks across vault
  • obs daily open --json — today's daily note (if exists)
  • obs files list --since 3d --sort modified --json — recently active files
  1. Analyze:
  • Group pending tasks by file/project
  • Check which tasks are in recently active files (high momentum)
  • Look for tasks with deadlines in frontmatter (due dates)
  • Check for tasks tagged with priority markers
  1. Recommend top 3 actions:

``` ## What to focus on now

### 1. [Task or action] From: [[source note]] Why now: [Has momentum / deadline approaching / blocking other work]

### 2. [Task or action] From: [[source note]] Why now: [reason]

### 3. [Task or action] From: [[source note]] Why now: [reason]

## Also on your plate

  • [Other pending items, grouped by area]

## Stale tasks (consider archiving)

  • [Tasks in files not modified for 2+ weeks]

```

  1. Offer to update the daily note with the focused plan

/decide — Gather evidence for a decision

When the user invokes /decide :

  1. Parse the decision question
  2. Search the vault for relevant context:
  • obs search content "" --json
  • obs search content "" --json
  • Check for notes explicitly about this topic
  1. Read relevant notes and extract:
  • Arguments for and against
  • Past experiences or lessons learned
  • Related decisions already made
  • Values or principles expressed
  1. Present the decision framework:

``` ## Decision:

### What your notes say

#### For

  • [Evidence from [[note]]]
  • [Evidence from [[note]]]

#### Against

  • [Concern from [[note]]]
  • [Concern from [[note]]]

### Related past decisions

  • [Previous decision from [[note]] and its outcome]

### Your values on this

  • [Principles or values expressed in relevant notes]

### What's missing

  • [Information you'd need that isn't in the vault]

### Bottom line [Based on your own notes, the evidence leans toward X because...] ```

  1. Emphasize: this is the user's own thinking reflected back, not new advice

/graduate — Promote buried ideas to standalone notes

When the user invokes /graduate:

  1. Scan daily notes and journal entries for buried ideas:
  • obs files list --folder "Daily" --sort modified --json (or detect daily note folder)
  • obs files list --since 2w --sort modified --json
  1. Read recent daily/journal notes and look for:
  • Ideas that deserve their own note (substantial paragraphs not about daily logistics)
  • Recurring themes across multiple days
  • Questions or hypotheses that were written once and never followed up
  • Links to notes that don't exist yet (broken links as idea signals)
  1. Also check: obs links broken --json — broken links are ideas waiting to be born
  2. Present candidates:

``` ## Ideas ready to graduate

### 1. "[Idea title]" Source: [[daily note]] (date) Original text: "[excerpt]" Why graduate: [Substantial thought / recurring theme / has connections] Suggested location: [folder/filename.md]

### 2. ...

## Broken links worth creating

  • [[missing-note]] — referenced by N notes
  • [[another-missing]] — referenced by M notes

```

  1. For each idea the user wants to graduate:
  • Create the new note with content expanded from the original excerpt
  • Add wikilinks back to the source
  • Add a wikilink from the source daily note to the new note
  • Set frontmatter: type, tags, graduated-from

Tips

  • /next should be opinionated. Don't just list everything — recommend a focus.
  • /decide must only use the user's own notes as evidence. Don't inject outside opinions.
  • /graduate is about recognizing when an idea has outgrown its container (daily note, journal entry).
  • Check for daily note folder config: the folder might be "Daily", "Journal", "Daily Notes", etc.

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.