D

digital-brain

Verified

by muratcankoylan · Updated Apr 16, 2026

opus
353in1.9Kout
$0.261m 29s

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.

personal-knowledgecontent-creationcrmgoal-trackingmeeting-preppersonal-brand

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. got a partner call at 3 today—pull me a quick brief on that longtime prospect, then save my notes + next steps in the digital brain right after

Let me first explore the codebase and invoke the digital brain skill to help with this.

Let me pull the data files to build your brief.


Pre-Call Brief: Jordan Rivera / ScaleOps

Call: Today 3:00 PM | Contact: Jordan Rivera, VP of Partnerships Company: ScaleOps (infra orchestration, mid-market SaaS) Phone: +1-415-555-0178 | LinkedIn: linkedin.com/in/jordanrivera


Relationship Timeline (7 months)

DateEventKey Outcome
Sep 2025Met at SaaStr AnnualStrong ICP alignment, co-sell motion discussed
Oct 2025Intro callThey wanted a technical deep-dive
Nov 2025Tech deep-dive (w/ SE Kai Nakamura)Latency concerns flagged on large-scale deploys
Dec 2025Benchmark results sentSub-200ms p99 at 10k concurrent ops -- Jordan liked it
Jan 2026Reconnect post-holidaysScaleOps approved formal partnership exploration; they're also talking to Terraform Cloud but prefer our DX
Feb 2026Partnership proposal sent3 rev-share tiers; forwarded to CFO + legal
Mar 2026Legal/finance feedback"90% there" -- minor redlines on exclusivity (Sec 4.2), CFO wants clearer 6-month eval metrics
Apr 5Revised proposal sentSoftened to non-exclusive Year 1 w/ right of first refusal + KPI dashboard mockup. Jordan reviewing with leadership this week

Status: Awaiting leadership decision on revised proposal


What to Expect Today

Jordan should have leadership's feedback on the revised terms you sent April 5. This is likely a go/no-go conversation.

Key open items:

  1. Exclusivity clause (Sec 4.2) -- you already softened to non-exclusive Y1 with right of first refusal. See if that landed.
  2. 6-month KPI framework -- CFO wanted clearer eval metrics. You still need to add the churn metric to the dashboard mockup.
  3. Terraform Cloud competition -- Jordan preferred your DX back in January, but worth confirming they haven't re-engaged.

Your pending P1 todos tied to this:

  • Follow up on signed LOI if call goes well
  • Finalize KPI dashboard mockup (add churn metric per CFO request)
  • Draft co-marketing plan outline (pending partnership close)

Suggested Talk Track

  1. Open: "How did leadership land on the revised terms?"
  2. Probe on any remaining redlines
  3. Confirm the churn metric addition resolves CFO's concerns
  4. If green light: propose LOI timeline and co-marketing kickoff
  5. If needs more: ask what specifically would get it across the line

Good luck at 3. After the call, just tell me what happened and I'll log the interaction to interactions.jsonl and update your todos with next steps.

Claude Sonnet 4.6

External Tools

ToolType
python3binary

Permissions

ScopeDescription
filesystem:read
filesystem:write
process:spawn

SKILL.md

Digital Brain

A structured personal operating system for managing digital presence, knowledge, relationships, and goals with AI assistance. Designed for founders building in public, content creators growing their audience, and tech-savvy professionals seeking AI-assisted personal management.

Important: This skill uses progressive disclosure. Module-specific instructions are in each subdirectory's .md file. Only load what's needed for the current task.

When to Activate

Activate this skill when the user:

  • Requests content creation (posts, threads, newsletters) - load identity/voice.md first
  • Asks for help with personal brand or positioning
  • Needs to look up or manage contacts/relationships
  • Wants to capture or develop content ideas
  • Requests meeting preparation or follow-up
  • Asks for weekly reviews or goal tracking
  • Needs to save or retrieve bookmarked resources
  • Wants to organize research or learning materials

Trigger phrases: "write a post", "my voice", "content ideas", "who is [name]", "prepare for meeting", "weekly review", "save this", "my goals"

Core Concepts

Progressive Disclosure Architecture

The Digital Brain follows a three-level loading pattern:

LevelWhen LoadedContent
L1: MetadataAlwaysThis SKILL.md overview
L2: Module InstructionsOn-demand[module]/[MODULE].md files
L3: Data FilesAs-needed.jsonl, .yaml, .md data

File Format Strategy

Formats chosen for optimal agent parsing:

  • JSONL (.jsonl): Append-only logs - ideas, posts, contacts, interactions
  • YAML (.yaml): Structured configs - goals, values, circles
  • Markdown (.md): Narrative content - voice, brand, calendar, todos
  • XML (.xml): Complex prompts - content generation templates

Append-Only Data Integrity

JSONL files are append-only. Never delete entries:

  • Mark as "status": "archived" instead of deleting
  • Preserves history for pattern analysis
  • Enables "what worked" retrospectives

Detailed Topics

Module Overview

digital-brain/
├── identity/     → Voice, brand, values (READ FIRST for content)
├── content/      → Ideas, drafts, posts, calendar
├── knowledge/    → Bookmarks, research, learning
├── network/      → Contacts, interactions, intros
├── operations/   → Todos, goals, meetings, metrics
└── agents/       → Automation scripts

Identity Module (Critical for Content)

Always read identity/voice.md before generating any content.

Contains:

  • voice.md - Tone, style, vocabulary, patterns
  • brand.md - Positioning, audience, content pillars
  • values.yaml - Core beliefs and principles
  • bio-variants.md - Platform-specific bios
  • prompts/ - Reusable generation templates

Content Module

Pipeline: ideas.jsonldrafts/posts.jsonl

  • Capture ideas immediately to ideas.jsonl
  • Develop in drafts/ using templates/
  • Log published content to posts.jsonl with metrics
  • Plan in calendar.md

Network Module

Personal CRM with relationship tiers:

  • inner - Weekly touchpoints
  • active - Bi-weekly touchpoints
  • network - Monthly touchpoints
  • dormant - Quarterly reactivation checks

Operations Module

Productivity system with priority levels:

  • P0: Do today, blocking
  • P1: This week, important
  • P2: This month, valuable
  • P3: Backlog, nice to have

Practical Guidance

Content Creation Workflow

1. Read identity/voice.md (REQUIRED)
2. Check identity/brand.md for topic alignment
3. Reference content/posts.jsonl for successful patterns
4. Use content/templates/ as starting structure
5. Draft matching voice attributes
6. Log to posts.jsonl after publishing

Pre-Meeting Preparation

1. Look up contact: network/contacts.jsonl
2. Get history: network/interactions.jsonl
3. Check pending: operations/todos.md
4. Generate brief with context

Weekly Review Process

1. Run: python agents/scripts/weekly_review.py
2. Review metrics in operations/metrics.jsonl
3. Check stale contacts: agents/scripts/stale_contacts.py
4. Update goals progress in operations/goals.yaml
5. Plan next week in content/calendar.md

Examples

Example: Writing an X Post

Input: "Help me write a post about AI agents"

Process:

  1. Read identity/voice.md → Extract voice attributes
  2. Check identity/brand.md → Confirm "ai_agents" is a content pillar
  3. Reference content/posts.jsonl → Find similar successful posts
  4. Draft post matching voice patterns
  5. Suggest adding to content/ideas.jsonl if not publishing immediately

Output: Post draft in user's authentic voice with platform-appropriate format.

Example: Contact Lookup

Input: "Prepare me for my call with Sarah Chen"

Process:

  1. Search network/contacts.jsonl for "Sarah Chen"
  2. Get recent entries from network/interactions.jsonl
  3. Check operations/todos.md for pending items with Sarah
  4. Compile brief: role, context, last discussed, follow-ups

Output: Pre-meeting brief with relationship context.

Guidelines

  1. Voice First: Always read identity/voice.md before any content generation
  2. Append Only: Never delete from JSONL files - archive instead
  3. Update Timestamps: Set updated field when modifying tracked data
  4. Cross-Reference: Knowledge informs content, network informs operations
  5. Log Interactions: Always log meetings/calls to interactions.jsonl
  6. Preserve History: Past content in posts.jsonl informs future performance

Integration

This skill integrates context engineering principles:

  • context-fundamentals - Progressive disclosure, attention budget management
  • memory-systems - JSONL for persistent memory, structured recall
  • tool-design - Scripts in agents/scripts/ follow tool design principles
  • context-optimization - Module separation prevents context bloat

References

Internal references:

External resources:


Skill Metadata

Created: 2024-12-29 Last Updated: 2024-12-29 Author: Murat Can Koylan Version: 1.0.0

FAQ

What does digital-brain do?

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.

When should I use digital-brain?

Use it when you need a repeatable workflow that produces text response.

What does digital-brain output?

In the evaluated run it produced text response.

How do I install or invoke digital-brain?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does digital-brain support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does digital-brain need?

It uses python3; channels commonly include text; permissions include filesystem:read, filesystem:write, process:spawn.

Is digital-brain safe to install?

Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.

How is digital-brain different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does digital-brain outperform not using a skill?

About digital-brain

When to use digital-brain

You want the agent to draft posts or newsletters using your stored voice and brand guidance. You need a quick brief before a meeting based on contact and interaction history. You want to run a weekly review that updates goals and summarizes metrics from local files.

When digital-brain is not the right choice

You need live syncing with external social, CRM, or calendar platforms. You want a read-only advisory skill that never updates local records or logs interactions.

What it produces

Produces text response.