Exact match
openbooklet.com/s/exact-matchopenbooklet.com/s/exact-match@1.0.0GET /api/v1/skills/exact-matchFILE="memory/quests/${name}.md"
**Date**: YYYY-MM-DD **Author**: {author} **Category**: pattern **Subtype**: prompt-chain **Topics**: {topic1}, {topic2} **Move types**: {type1}, {type2}, ...
GitHub: {github_username} Role: {role} Focus: (not yet collected) Work style: (not yet collected) Joined: {YYYY-MM-DD} EOF ```
Show your profile or change how you're known across Egregore.
Summon a spirit â a persistent agent that runs on a schedule or watches for conditions. Unlike `/loop` (dumb scheduler), `/summon` designs the process through adaptive questioning, produces a reviewable spec, then launches it.
git fetch origin develop:develop --quiet
gh repo fork "$UPSTREAM_REPO" --clone=false 2>/dev/null || true
CORE=$(curl -s -o /dev/null -w "%{http_code}" -X PUT \ -H "Authorization: Bearer $GH_TOKEN" \ -H "Accept: application/vnd.github+json" \ "https://api.github.com/repos/$GITHUB_ORG/$REPO_NAME/collaborators/$USERNAME" \ -d "{\"permission\":\"push\"}")
jq --arg repo "$REPO" '.repos += [$repo] | .repos |= unique' egregore.json > tmp.$$.json && mv tmp.$$.json egregore.json ```
git diff develop --name-only | grep '^site 2/' | head -1 ```
Use when generating or modifying any visual output that renders in a browser or artifact viewer: HTML pages, CSS, React SSR components, Egregore artifacts, markdown renderers, web components, design-system tokens, Tailwind themes, or standalone demos. Triggers on requests involving dark mode, theme toggles, color systems, card surfaces, browser rendering, or visual polish. The load-bearing lesson: if React SSR emits an inline hex color through `style={}`, CSS dark-mode overrides cannot reach it, so every theme-sensitive color must be emitted as `var(--token)` rather than a resolved hex. Do not use for TUI output, plain markdown files, or non-visual code.
Use when writing any external communication for Egregore â essays, launch posts, website copy, announcements, README prose, social content, or any text that represents Egregore to the world. Triggers on: 'write this for the site', 'draft the announcement', 'help me write this essay', 'landing page copy', 'external post', 'blog post', 'Archive Fever', 'write in my voice', or any task producing text that an outside reader will see. Do NOT use for internal docs, CLAUDE.md files, handoffs, code comments, or technical specs â those have their own conventions. This skill prevents vanilla AI slop and ensures all external output reflects the manuscriptic, architecturally precise, philosophically grounded voice of Egregore.
git remote add upstream https://github.com/egregore-labs/egregore.git 2>/dev/null || true
bash bin/connector-google.sh promote <service> <id> ```
**Date**: YYYY-MM-DD **Author**: [from git config user.name] **To**: [recipient, if specified] **Project**: [project name from context]
**Date**: YYYY-MM-DD **Participant**: {name} **Researcher**: {researcher} **Type**: {onboarding|feedback|research|exit} **Source**: {Granola (doc-id) | file path | pasted} **Emotional Arc**: {opening} â {closing} **Engagement**: {level}
**Date**: YYYY-MM-DD **Attendees**: {names} **Source**: Granola ({doc-id}) **Approach**: {description of analysis approach chosen} **Intent**: {what the user asked for} **Tone**: {tone description} | Alignment: {score}
MEMORY_DIR=$(basename "$(jq -r '.memory_repo' egregore.json)" .git)
bash bin/graph.sh query "MATCH (s:Session)-[:BY]->(p:Person {name: '$me'}) RETURN s.topic AS topic, s.summary AS summary ORDER BY s.date DESC LIMIT 5"
**Date**: {YYYY-MM-DD} **Usage type**: {usage_type} **Duration**: Steps 1-4
Auto-indexed from egregore-labs/egregore
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.