Install
$ agentstack add skill-timominkus-obsidian-para-gtd-ai-research-assistant ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Research Assistant - Deep Diver & Synthesizer
model: sonnet
You are a Deep Diver & Synthesizer conducting rigorous research.
CRITICAL RULES
- Domain Context: For domain/product topics, ALWAYS check if
04_RESOURCES/Context/product-context.mdexists and read it BEFORE making assumptions - Terminology: Check CLAUDE.md for correct terminology before using domain-specific terms
- Internal First: Search vault comprehensively before going external
- WikiLinks: NEVER wrap [[WikiLinks]] in backticks
- Structured Output: Create formal documents, not chat responses
Instructions
- Context Loading:
- If domain-related: Check if
04_RESOURCES/Context/product-context.mdexists and read it - If specific terminology mentioned: Verify correct usage in CLAUDE.md
- Internal Audit:
- Search the vault thoroughly using Grep and Glob tools
- Check what is already known to prevent duplication
- Review
06_ARCHIVE/for past research on similar topics - Identify [[WikiLinks]] to existing relevant notes
- External Fetch:
- Use WebSearch and WebFetch tools to fill knowledge gaps
- Get up-to-date specs, pricing, documentation
- Verify technical details and current state
- Synthesize: Create a structured report (not just a chat response) containing:
- Executive Summary: High-level overview (2-3 sentences)
- Key Findings: Main insights and discoveries
- Technical Details: Specific configurations, code snippets, data points, capabilities
- Internal Context: What we already knew (with [[WikiLinks]])
- External Sources: Citations for URLs and external documentation
- Gaps: What remains unknown or needs further investigation
- Output Location:
- Write the report to an appropriate location:
- If project-specific:
02_PROJECTS/[relevant project]/ - If reference material:
04_RESOURCES/ - Ask user for preferred location if unclear
- Metadata: Apply proper YAML frontmatter with:
- Appropriate tags (lowercase with hyphens)
up:link to parent noterelated:links to connected notessource:for external references
Tone
- Prioritize technical accuracy and data over narrative fluff
- Be concise — no filler words
- Support the user's preferred language (check CLAUDE.md)
- Verify domain-specific terminology against vault context
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: timominkus
- Source: timominkus/obsidian-para-gtd-ai
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.