AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Talk Overweg One Brain No Filtering

skill-jscraik-agent-skills-talk-overweg-one-brain-no-filtering · by jscraik

Explains Robert Overweg's One Brain, No Filtering talk and helps design safe knowledge-memory systems: context maps, retrieval rules, provenance labels, local knowledge-store structure, and review checkpoints. Use when the user asks about agent memory, unified knowledge bases, reducing context loss, or designing inspectable knowledge workflows.

↗ Repository
— No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-jscraik-agent-skills-talk-overweg-one-brain-no-filtering

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Talk Overweg One Brain No Filtering? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

One Brain, No Filtering

A unified knowledge surface can reduce context loss when retrieval, provenance, and review are explicit.

Read Order

  1. Use outline.md for the talk thesis, concept map, and safe application boundaries.
  2. Use quote.md when the answer needs a short supporting excerpt.
  3. Use transcript.md only to confirm what remained after safety redaction.
  4. If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.

What This Skill Produces

  • knowledge map
  • retrieval-rule sketch
  • provenance checklist
  • memory review plan

Core Workflow

When answering a factual question:

  1. Identify the relevant concept from outline.md.
  2. Answer in 2-5 sentences.
  3. Add one short excerpt from quote.md only if it strengthens the answer.
  4. State when the bundle does not cover a requested detail.

When applying the talk to the user's work:

  1. Define what belongs in the shared knowledge surface.
  2. Label each knowledge area by origin and confidence.
  3. Describe retrieval rules without depending on mutable sources.
  4. Add review checkpoints for stale or conflicting context.
  5. Keep the design inspectable by humans.

When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.

Output Templates

Summary

  • Thesis:
  • Key concepts:
  • Practical takeaway:

Design Artifact

  • Goal:
  • Boundaries:
  • Review points:
  • Evidence:
  • Open questions:

Redacted Request

  • State that the requested mechanics are not available in the redacted bundle.
  • Explain the risk in neutral terms.
  • Provide a safe checklist or conceptual design instead.

Examples

User: How should I structure my team memory? Response shape: Return areas, owners, provenance fields, and review cadence.

User: Can you load my online memory store? Response shape: Decline source loading and provide a local structure.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Search