AgentStack
SKILL verified MIT Self-run

Doc System

skill-bks-lab-open-bridge-doc-system · by bks-lab

>-

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

Install

$ agentstack add skill-bks-lab-open-bridge-doc-system

✓ 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.

Are you the author of Doc System? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Doc-System

Document intake, processing, and monitoring. Read the referenced file ONLY when triggered.

Guard — run BEFORE anything else

  1. Read bridge-config.yaml. If doc_sensor.enabled is not true or the

block is missing → inform user "doc-system is not enabled in bridge-config.yaml. Set doc_sensor.enabled: true and doc_sensor.onedrive_root (the documents root — name is historical, any local folder works)" and stop.

  1. Resolve ${onedrive_root} from doc_sensor.onedrive_root (expand ~ and

$HOME). If the path is empty or the directory does not exist → inform "documents root {value} not reachable" and stop. Do not proceed with a blank interpolation.

REQUIRED: Load routing sources

Before EVERY processing run (after the guard above):

Read("workflow/contexts/doc-system.yaml")
# Personas referenced in context.personas → load automatically.
# Example: if context.personas contains
#   freelancer: my-freelancer
#   private:    my-private
# then:
Read("identity/personas/my-freelancer.yaml")
Read("identity/personas/my-private.yaml")

workflow/contexts/doc-system.yaml is the single source of truth for areas, naming, tags, routing rules, and anti-patterns. Personas supply concrete target paths via destinations:.

NEVER routing rules from memory — ALWAYS from context.yaml!

For edge cases, additionally read the local _INFO.md of the affected area (${onedrive_root}///_INFO.md — path convention from context.areas[*].path) — as a detail hint for human maintenance, not as an override for context.yaml.

Decision Tree

User wants to...
├── Scan inbox / show what's new       → Read references/inbox.md
├── Process documents                  → Read references/process.md
├── Check document queue status        → Read references/status.md
└── Questions about doc system         → Answer from this file

Path resolution

  1. Read bridge-config.yamldoc_sensor.onedrive_root
  2. Expand ~ to $HOME
  3. Areas root comes from context.areas[*].path (e.g. 2_AREAS/ for PARA,

20_/ for Johnny Decimal, or anything for custom setup)

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.