50fa79407d
Some checks are pending
CI — CoM Config Validation / Validate JSON Configs (push) Waiting to run
CI — CoM Config Validation / Validate YAML Configs (push) Waiting to run
CI — CoM Config Validation / Lint Shell Scripts (push) Waiting to run
CI — CoM Config Validation / Secret Detection (push) Waiting to run
CI — CoM Config Validation / Lint Markdown (push) Waiting to run
CI — CoM Config Validation / Validate CODEOWNERS (push) Waiting to run
Public, sanitized mirror of an AI orchestration command center: agents, skills, MCP servers, slash-command workflows. All infrastructure identifiers, hostnames, mesh IPs/subnets, repo paths, maintainer identity, and hardware fleet specifics scrubbed to <placeholders>; session debug logs and host-specific memory removed. No live credentials. Verified clean by automated leak sweep. See SANITIZATION.md. churchofmalware.org . authorized research only
1.8 KiB
1.8 KiB
| name | description | argument-hint | allowed-tools | |
|---|---|---|---|---|
| research | Deep research workflow. Searches web, checks Notion knowledge base for existing research, then produces a structured research document and optionally saves to Notion. |
|
Bash, Read, Grep, Glob, Agent, WebFetch, WebSearch |
Deep research on: $ARGUMENTS
Research Protocol
Phase 1: Check Existing Knowledge
- Search the Notion workspace for existing research on this topic (use Notion search MCP)
- Check the Library of Nerd, Lib_CYBR, and Google Docs Starred Import for related docs
- Check the Syn_OS Knowledge Hub if topic is infrastructure/security related
- Report what already exists — avoid duplicating research
Phase 2: Web Research
- Search the web for current, authoritative sources on the topic
- Prioritize: official documentation, academic papers, established security resources, recent (2025-2026) technical blogs
- Gather at least 5 distinct sources
- Extract key facts, frameworks, and actionable insights
Phase 3: Synthesize
Produce a structured research document with:
- Executive Summary (3-5 sentences)
- Key Findings (bulleted, with source citations)
- Technical Details (toggle sections for depth)
- Relevance to CoM/Syn_OS (how this connects to current work)
- Action Items (concrete next steps)
- Sources (linked references)
Phase 4: Save (Optional)
Ask the user if they want to save the research to Notion. If yes:
- Determine the best Target Section (AI Agents, OS Hardening, DevSecOps, ARCANUM Reference, Kernel Dev, Business/GTM, General Research)
- Create or update the appropriate condensed research page
- Add an entry to Google Docs Starred Import DB if this originated from a Google Doc
- Update cross-references in related pages