architecture-review
Surfaces architectural friction in real code — shallow modules, tight coupling, untested seams — and proposes deepening refactors…
LinkedIn + personal brand system for founders. Apply when drafting LinkedIn posts, reactions, DMs, LinkedIn About sections, or planning LLM visibility.
$ npx -y skills add assafkip/kipi-system --skill linkedin-brand --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/linkedin-brandContext preview
The summary Claude sees to decide when to auto-load this skill.
LinkedIn + personal brand system for founders. Apply when drafting LinkedIn posts, reactions, DMs, LinkedIn About sections, or planning LLM visibility.
name: linkedin-brand description: "LinkedIn + personal brand system for founders. Apply when drafting LinkedIn posts, reactions, DMs, LinkedIn About sections, or planning LLM visibility."
This skill is the operating system for a founder's LinkedIn presence and broader LLM visibility. It enforces the 2026 algorithm reality (360Brew decoder-only LLM), provides summary frameworks, and governs the cross-platform entity graph that makes a founder legible to ChatGPT, Claude, Gemini, and Perplexity.
Auto-fire on any of these:
Skip for: internal ops chat, code, system files.
Always read in this order: 1. `references/playbook.md` — format rules, cadence, first-hour rule 2. `references/voice-check.md` — AI-detection patterns to avoid 3. `references/summary-frameworks.md` — if drafting/editing an About section 4. `references/llm-visibility.md` — if question is about broader visibility
Then read instance-specific files (not bundled in the skill):
If those instance files do not exist, ask the founder to create them before drafting. Do not invent pillars or positioning.
All patterns below are enforced deterministically by `kipi_voice_lint` and `kipi_copy_edit_lint` during the Pre-Publish Checklist. No memory-based self-check.
**Enforced by `kipi_voice_lint` / `kipi_copy_edit_lint`:**
If a pattern keeps slipping past, extend `draft_scanner.py` or `linter.py`. Never add rules to this file that ask Claude to remember.
See `references/voice-check.md` for the teaching reference.
Before drafting a reaction (comment, reply, quote-post, DM about someone's content): 1. Extract the poster's claims verbatim. No interpretation. 2. Show extracted claims to the founder. Do not draft until confirmed. 3. Draft in founder voice. Reactions are about the poster's ideas, not your product. 4. Self-check: zero product name-drops unless founder explicitly asked.
Run in this order. Drafting is never blocked by cadence — only the final ship decision is.
When drafting a new original post, call `kipi_linkedin_cadence_check()` and surface the result to the founder. Do NOT block the draft — the founder may be preparing a post for a later week, or deliberately overriding the cap.
Skip Step 0 entirely when drafting a comment, reply, DM, or About section.
Call `kipi_linkedin_gate(draft, kind, day_of_week, override_day)`. Pass `kind`
Give your AI the right knowledge, at the moment it needs it. Kipi turns the scattered knowledge around your work into context that follows you across AI sessions: decisions, conversations, projects, people, commitments, lessons, documents, history.
Surfaces architectural friction in real code — shallow modules, tight coupling, untested seams — and proposes deepening refactors…
AUDHD executive function accommodations. Apply to all output the founder will act on.
Generate modern presentation decks (PDF) from markdown content. Local open-source alternative to Gamma — uses Slidev for layouts…
Founder voice enforcement for all written output. Apply to any text another person will read.
Platform-optimized headline and hook engineering for X (Twitter), Reddit, LinkedIn, Medium, Substack. Apply when writing or…