foryourhealth111-pixel/Vibe-Skills / bundled/skills/digital-brain
digital-brain
VerifiedThis 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.
network/NETWORK.md
View on GitHub---
name: network-module
description: Relationship and contact management - people you know, interaction history, and networking notes. Use before meetings, when connecting people, or managing relationships.
---
# Network Module
Your personal CRM for meaningful relationships.
## Files in This Module
| File | Format | Purpose |
|------|--------|---------|
| `contacts.jsonl` | JSONL | People database |
| `interactions.jsonl` | JSONL | Meeting/conversation log |
| `circles.yaml` | YAML | Relationship tiers and groups |
| `intros.md` | Markdown | Pending/made introductions |
## Data Schemas
### Contact Entry
```json
{
"id": "contact_[unique]",
"created": "ISO8601",
"updated": "ISO8601",
"name": "Full Name",
"handle": "@twitter_handle",
"email": "email@domain.com",
"company": "Company Name",
"role": "Their Role",
"location": "City, Country",
"circle": "inner|active|network|dormant",
"how_met": "How you met",
"relationship": "friend|mentor|peer|collaborator|investor|customer",
"topics": ["topic1", "topic2"],
"can_help_with": ["what they can help you with"],
"you_can_help_with": ["how you can help them"],
"notes": "Personal notes",
"last_contact": "ISO8601",
"links": {
"twitter": "url",
"linkedin": "url",
"website": "url"
}
}
```
### Interaction Entry
```json
{
"id": "int_YYYYMMDD_HHMMSS",
"date": "ISO8601",
"contact_id": "contact_[id]",
"type": "call|coffee|dm|email|event|collab",
"context": "What you discussed",
"key_points": ["point1", "point2"],
"follow_ups": ["action1", "action2"],
"sentiment": "positive|neutral|needs_attention"
}
```
## Workflows
### Before a Meeting
1. Look up contact in `contacts.jsonl`
2. Review recent interactions in `interactions.jsonl`
3. Check `circles.yaml` for relationship context
4. Note any pending follow-ups or intros
### After a Meeting
1. Log interaction in `interactions.jsonl`
2. Update `last_contact` in contacts.jsonl
3. Add any follow-ups to operations/todos.md
4. Update relationship notes if needed
### Making Introductions
1. Check both contacts in `contacts.jsonl`
2. Ensure mutual value (check can_help_with fields)
3. Log in `intros.md`
4. Track follow-through
## Agent Instructions
<instructions>
When managing relationships:
1. **Looking up contacts**: Search by name, handle, company, or topics
2. **Pre-meeting prep**: Compile contact info + recent interactions + shared interests
3. **Logging interactions**: Always include date, type, context, and follow-ups
4. **Intro matching**: Cross-reference can_help_with fields
5. **Relationship maintenance**: Flag contacts with stale last_contact dates
Circle definitions:
- inner: Close relationships, regular contact
- active: Current collaborators, frequent interaction
- network: Known contacts, periodic touchpoints
- dormant: Historical connections, may reactivate
</instructions>
## Relationship Principles
```yaml
networking_philosophy:
- "Give before you ask"
- "Quality over quantity"
- "Follow up is everything"
- "Be genuinely helpful"
- "Make warm intros, not cold"
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |