Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

setup-obsidian

Estrelas2

Forks1

Atualizado17 de maio de 2026 às 01:09

Scaffold an Obsidian vault config over `<config-root>/`. After this runs, the user can open Obsidian → File → Open vault → select <config-root>/ and see their cortex memory as a graph, with daily-brief snapshots as daily notes and a VAULT.md home page powered by Dataview. Auto-fires when the user says: "set up Obsidian", "make this work in Obsidian", "enable graph view", "make this work on mobile", "I want to use Obsidian", "set up a vault", "configure Obsidian", "open this in Obsidian". Idempotent and non-destructive — existing `.obsidian/` files and VAULT.md are preserved on re-run. Force-reset available via `/setup-obsidian --reset`.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

BrightWayAI

BrightWayAI/claude-cortex

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name

setup-obsidian

description

setup-obsidian

See commands/setup-obsidian.md for the full workflow.

When to fire

Explicit: /setup-obsidian or any trigger phrase above.
Implicit cross-skill: if /setup-identity finishes and the user mentions Obsidian or mobile access in the conversation, offer to chain into /setup-obsidian.

What to do

Resolve <config-root> and read identity for personalization.
Confirm the plan (which files will be written, which preserved).
Write .obsidian/app.json, core-plugins.json, daily-notes.json (skip existing).
Write VAULT.md (skip existing).
Inform about daily-brief and memory-index integration status.
Report.

What this skill does NOT do

Does not install Obsidian.
Does not install Obsidian community plugins (it lists them, user clicks through).
Does not modify any other plugin's behavior. Pure config scaffolding.
Does not overwrite existing user files unless --reset is explicitly passed and re-confirmed per file.

Mais deste repositório

mesmo repositório

end-day

BrightWayAI/claude-cortex

End-of-day closing routine. Quick mode by default (v4.6+) — runs cortex auto-commit, reflective prompts, brief pre-stage, memory-index refresh, and close in 30 seconds to 3 minutes. Heavy steps (inbox triage, transcript review, mining of non-transcript sources) only run in `/end-day --full`, or when auto-offered because the day actually had transcripts (≥2) or inbox volume (≥5). Auto-fires on "/end-day", "wrapping up", "calling it a day", "done for today", "end of day", "closing out today". Quick mode is the default for every trigger; the user passes `--full` or accepts the auto-offer prompt to get the full chain. Reflection (Step 4) appends a `## Reflection` section to today's brief markdown — what tomorrow's `/brief` reads — AND to a longitudinal `memory/reflections.md` store (v4.13+). v4.13+ additions (End-Day Routine Improvement Spec): a per-source consent + cost gate (Step 0.7, Today's Brief required & first); Step 2c mines the brief artifact (task/outreach actions → memory write-backs + suppression lear

2026-06-082

sync-linked-entities

BrightWayAI/claude-cortex

Natural-language entrypoint for cross-artifact drift detection. Fires when the user has just made a meaningful change to a node (status flip, reframe, engagement wound down) and says "check the linked nodes," "sync linked artifacts," "make sure the related stuff is consistent," or similar. Resolves the source node from recent edit or context, then routes to /sync-linked-entities.

2026-05-282

relink-memory

BrightWayAI/claude-cortex

Retroactive wikilink pass over `<config-root>/memory/`. Scans every node file for plain-text mentions of known entities (people / clients / topics / workstreams / companies / domains), proposes converting them to `[[wikilinks]]`, and graduates heavily-mentioned persons into person pages. One-time migration per cortex v4.10+. Idempotent; gated by `memory/.migration-wikilink-relink-done` marker. Run once after upgrading; future memory writes use wikilinks natively per the canonical rule in cortex CLAUDE.md. Auto-fires when the user says: "relink my memory", "fix my wikilinks", "my graph is disconnected", "why isn't my obsidian graph showing edges", "back-fill the wikilinks", "graduate the people in my memory". Use `--rerun` to force re-scan after marker exists. Cost: 1-3 min for ~30 nodes. Token cost ~$0.10-0.50 per run.

2026-05-212

start-workstream

BrightWayAI/claude-cortex

Create a new workstream node — cortex's primitive for ongoing initiative pipelines that span multiple projects, people, and topics. Walks a short interview (name, current state, pinned context, linked entities) and writes `<config-root>/memory/workstream/<slug>.md`. Auto-fires when the user says: "start a workstream", "begin tracking X as a workstream", "I'm starting a new initiative — X", "I'm working on a new initiative", "set up a workstream for X". Differentiation: - Project nodes (`client/<slug>`) capture a specific engagement. - Person pages capture a relationship. - Topic nodes capture a subject area. - Domain nodes capture a persistent area of work. - Workstreams capture an ongoing *initiative pipeline* with current state, pinned context, open loops, and linked entities — spans projects/people/topics. New in cortex v4.9.0. See `references/workstream-schema.md` for the full schema.

2026-05-212

indexer

BrightWayAI/claude-cortex

Regenerate `<config-root>/memory/index.md` — a deterministic, zero-LLM catalog of every memory node grouped by type with decay-state flags. Auto-fires in THREE scenarios: 1. CHAIN STEP: invoked as Step 6 of `/end-day` and as the final step of `/cleanup`. Runs after user-gated changes are committed so the index reflects current state. 2. DEFERRED: when `/remember` writes a new entry, it appends a line to `<config-root>/memory/staged/queues/reindex`. The next `/end-day` or `/cleanup` notices the queue and runs the indexer. 3. EXPLICIT: user runs `/reindex`, or says "regenerate the memory index", "rebuild the catalog", "refresh memory/index.md". This skill has zero LLM cost in steady state. It is a file-walk + string-extract + write. No reasoning, no synthesis — see references/memory-index.md for the deterministic spec.

2026-05-212

listen

BrightWayAI/claude-cortex

Nightly autonomous ingest pipeline. Pulls yesterday's calendar / Gmail / Slack / transcripts / Drive activity into `<config-root>/archive/YYYY-MM-DD/` (immutable substrate), runs the mining agents against the archive, stages all proposed memory commits to `staged/commit-drafts/YYYY-MM-DD.md`, and refreshes `memory/hot.md`. Designed for unattended scheduled execution — no user gates. Auto-fires when the user says: "ingest yesterday", "run nightly ingest", "what happened yesterday I haven't captured", "mine yesterday's calendar", "process yesterday's transcripts". Most users register it on a schedule (11pm or 5am) via core-ops `/register-schedules` and never invoke it by hand. Pair with `/morning` for the interactive review-and-merge of the staged draft.

2026-05-212

name

setup-obsidian

description

setup-obsidian

See commands/setup-obsidian.md for the full workflow.

When to fire

Explicit: /setup-obsidian or any trigger phrase above.
Implicit cross-skill: if /setup-identity finishes and the user mentions Obsidian or mobile access in the conversation, offer to chain into /setup-obsidian.

What to do

Resolve <config-root> and read identity for personalization.
Confirm the plan (which files will be written, which preserved).
Write .obsidian/app.json, core-plugins.json, daily-notes.json (skip existing).
Write VAULT.md (skip existing).
Inform about daily-brief and memory-index integration status.
Report.

What this skill does NOT do

Does not install Obsidian.
Does not install Obsidian community plugins (it lists them, user clicks through).
Does not modify any other plugin's behavior. Pure config scaffolding.
Does not overwrite existing user files unless --reset is explicitly passed and re-confirmed per file.