Skip to content

docs(skills): add proactive-agents experience rules - #6545

Closed
benjaminshafii wants to merge 1 commit into
devfrom
docs/proactive-agents-skill
Closed

benjaminshafii wants to merge 1 commit into
devfrom
docs/proactive-agents-skill

Conversation

@benjaminshafii

Copy link
Copy Markdown
Member

What is this about?

A repo skill, proactive-agents, that agents load before building anything that acts or messages people without being asked: Automations and triggers, Your agent, watches, notifications, Slack or email delivery.

What problem does it solve?

Proactive features are being built in parallel by several agents and people. Without shared rules, each one invents its own notification path, timing defaults and permission behavior, and the experience drifts toward noisy, surprising or silent agents.

What was the situation before?

The learnings from studying Grok Bot, OpenAI dots, Claude Duet, Meta Muse and OpenClaw lived only in chat threads. Nothing in the repo told an agent to stay silent by default, say why it messaged, send from its own identity, or wait for approval before irreversible actions.

How is this implemented?

  • New .opencode/skills/proactive-agents/SKILL.md: 14 experience rules, what the skill deliberately leaves open (architecture), how to check the work (replayed days, injection test, production mute rate), signs it was skipped, and where each rule comes from.
  • Strict about the experience, open about the solution, so it applies to Automations, Your agent and future channels alike.

What else changed?

none

Release note

none

Evidence

Docs-only change to agent guidance; no spec.

Signed-off-by: Benjamin Shafii <ben@prologe.io>
@vercel

vercel Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
openwork-app Ready Ready Preview Oct 27, 2026 5:17am UTC
openwork-den Ready Ready Preview Oct 27, 2026 5:17am UTC
openwork-diagnostics Ready Ready Preview Oct 27, 2026 5:17am UTC
openwork-landing Ready Ready Preview, v0 Oct 27, 2026 5:17am UTC

Request Review

@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

OpenWork evidence

Status Commit Preview Updated
⚪ No new preview dc8eec7 View run 2026-10-27 05:17:46 UTC

No change-specific evidence selected

@diff-warden diff-warden Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warden clearance. Complete security and confidentiality review of dc8eec75150cfe1d4ebac67d20e61cbc47be78f0 found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run

@diff-warden

diff-warden Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

Warden: approved

No high or medium security findings and no confidentiality findings.

Reviewed dc8eec75150c · Warden run · Updates after every Warden run.

@benjaminshafii

Copy link
Copy Markdown
Member Author

Closing: we're keeping only the Slack routing PR and the calendar-trigger PR open for now. The branch is kept, so this work isn't lost.

This branch was successfully deployed

4 active deployments
Preview – openwork-app — dc8eec75 Deployed Oct 27, 2026 by vercel[bot]
Preview – openwork-landing — dc8eec75 Deployed Oct 27, 2026 by vercel[bot]
Preview – openwork-den — dc8eec75 Deployed Oct 27, 2026 by vercel[bot]
Preview – openwork-diagnostics — dc8eec75 Deployed Oct 27, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant