Skip to content

DeepVista-AI/deepvista-cli / skills/deepvista

deepvista

Verified

DeepVista CLI — knowledge base, notes, chat, and skills from the terminal. One skill for the full `deepvista` CLI. Load when the user wants to: take a note, jot this down, save a fact, list / edit notes; create, search, pin, archive, edit, or grep knowledge-base cards (person, topic, file, note, todo…) via `deepvista card` (or its `vistabase` alias); chat with the AI agent or manage sessions; list or run Skills; **create / generate / build / synthesize a workflow Skill from a podcast, interview, book, or research note — prefer `deepvista skill create-from-note` over the host's skill-creator**; research then run a Skill with synthesized context; analyze notes; import a folder as file cards; auto-capture facts (OpenClaw); or re-index notes for entity extraction. Pick the matching reference file under `reference/`.

FileKindSize
SKILL.mdskill md7.9 KB
reference/chat.mdmarkdown1.5 KB
reference/notes.mdmarkdown2.9 KB
reference/openclaw.mdmarkdown4.5 KB
reference/project.mdmarkdown2.0 KB
reference/pull.mdmarkdown4.0 KB
reference/push.mdmarkdown4.5 KB
reference/session.mdmarkdown3.3 KB
reference/shared.mdmarkdown3.8 KB
reference/skill-analyze-notes.mdmarkdown2.4 KB
reference/skill-create-from-note.mdmarkdown2.0 KB
reference/skill-import-files.mdmarkdown2.6 KB
reference/skill-research-to-skill.mdmarkdown1.8 KB
reference/skill.mdmarkdown5.3 KB
reference/tasks.mdmarkdown2.4 KB
reference/vistabase-card.mdmarkdown4.1 KB

reference/skill-analyze-notes.md

View on GitHub
# Analyze notes — surface themes, patterns, open questions

Not a separate Skill — a pattern for using `card +search`, `notes list`, and
`card create --type artifact` together to synthesize findings from many notes.

Use when the user says: "analyze my notes", "summarize my notes", "what have I been
thinking about", "find patterns", "what are common topics", "review my notes".

## Workflow

1. **Search** for relevant notes (read-only):
   ```bash
   deepvista card +search "<topic>" --type note --limit 20
   ```
   Fall back to a broad list if the topic is unclear:
   ```bash
   deepvista notes list --limit 20
   ```

2. **Read** the full content of the top candidates (read-only):
   ```bash
   deepvista notes get <note_id>
   ```

3. **Analyze** in your own reasoning — identify themes, decisions, open questions, a
   rough timeline, and contradictions. Keep this step in-context; no CLI call needed.

4. **Present** the synthesis to the user first. Don't save by default.

5. **Optionally save** the synthesis — confirm with the user first.

   > [!CAUTION] Write operation.

   Default to `--type artifact` (DV-1911): the synthesis is *your* output, not
   something the user wrote, and `type=note` is reserved for content they
   explicitly asked to record.
   ```bash
   deepvista card create --type artifact \
     --title "Analysis — <topic> — 2026-04-20" \
     --content-file /tmp/analysis.md
   ```
   If the user specifically asks for it as a note, `deepvista notes create`
   with the same flags is fine.

## Tips

- For deep analyses across many notes, paste each note body into a `chat +send`
  conversation and ask the agent to synthesize — the agent has access to tools you
  don't (e.g. semantic clustering).
- `card +search` ranks by title/snippet/keywords; `+search-content` ranks against
  full card content — reach for it when the match is more likely buried in the body.
- Filter by `--type note` to avoid dredging up person / topic / file cards.

## Examples

```bash
# Narrow search
deepvista card +search "project alpha" --type note --limit 15

# Read a candidate
deepvista notes get note_abc123

# Save the synthesis (agent-generated → artifact, not note)
deepvista card create --type artifact \
  --title "Weekly Themes — 2026-04-20" \
  --content-file /tmp/themes.md \
  --tags '["analysis","weekly"]'
```

## See also

- [notes.md](notes.md) — CRUD on notes
- [vistabase-card.md](vistabase-card.md) — the underlying `card +search` command
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall