Skip to main content
Dash2Grow
Start free trial

Skill.md

negation-prose

Skill where brain reference precedes a negation-prose mention

negation-prose/

View on GitHub (opens in a new tab)

SKILL.md

---
name: negation-prose
description: Skill where brain reference precedes a negation-prose mention
triggers:
  - "do research"
---

# negation-prose

This skill starts with `gbrain search`, then talks about NOT using
web_search before the brain — testing that the position-relative check
correctly resolves to compliant (brain ref appears first in body).

## Workflow

1. Always start with `gbrain search "topic"` for existing context.
2. Do NOT use web_search before checking the brain. The brain has the
   answer 90% of the time.
3. Only after step 1 is empty, fall back to perplexity for fresh data.

Related Skill.md files

All Skill.md files →
Skill.md
gbrain/
  • SKILL.md
---
name: gbrain
description: Search and write the company knowledge brain. Use for any question about the org, people, projects, decisions, or history, and to persist durable knowledge beyond this scope's notebook.
---

gbrain

Skill.md
reference-pack/
  • SKILL.md
---
name: reference-pack
description: Reference skill demonstrating the 10/10 skillpack contract. Adds a "what does this skillpack do" answer to the user's agent.
---

reference-pack

Skill.md
brain-ingest-gate/
  • SKILL.md
---
name: brain-ingest-gate
description: Pre-write quality gate for content entering the brain. No raw copies: a bare cp/mv into the brain repo is a bug. Before any new page lands, resolve named entities registry-first (a vector score is a floor for prose, never a gate for named things), then run the read-the-top-hit dedup decision tree (clear-dup / plausible-dup / clear). Owns dedup; delegates enrichment to the shipped ingestion skills. Routing convention, not an operation-boundary enforcement.
---

brain-ingest-gate

Skill.md
brain-link-discipline/
  • SKILL.md
---
name: brain-link-discipline
description: When you report a brain page to the user — created, edited, committed, or
relayed from a subagent — a working link is part of the deliverable, in the
SAME message. Derive the path mechanically (git ls-files --full-name), push
BEFORE linking, verify the link resolves when a hosted remote exists, and
degrade through a defined fallback chain when it doesn't. Inside brain
pages the rule inverts: relative links preserve the link graph; absolute
URLs are for chat deliverables only.
---

brain-link-discipline