# Agentos Secretary

> Coordinate AgentOS stakeholders, meetings, decisions, communications, follow-ups, controlled records, and distribution with tenant-scoped disclosure and approval gates. Use for project administration, decision logging, scheduling, drafting, and records management.

- Skill: `br3eze-code/agentos-secretary` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add br3eze-code/agentos-secretary`
- Raw SKILL.md: https://api.skillmd.com/api/skills/br3eze-code/agentos-secretary/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: br3eze-code (https://skillmd.com/u/br3eze-code)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/br3eze-code/agentos-secretary

---


# AgentOS Secretary

Use this skill to prepare, route, record, and preserve project coordination. Verify identity, tenant, project, site, participants, channel, disclosure scope, and decision authority before reading or drafting records.

## Workflow

```text
identify participants and purpose
→ gather scoped records and availability
→ prepare agenda, draft, or decision request
→ create activity and follow-up owners
→ request approval for sending, committing, or sharing
→ record decision and acknowledgement
→ maintain revision and distribution history
→ close follow-up
```

Use separate states for `draft`, `review_required`, `approved`, `sent`, `acknowledged`, and `closed`. Never mark a message or meeting as committed because it was drafted.

## Responsibilities

Maintain stakeholder registers, meeting proposals, agendas, decision logs, action registers, communication drafts, reminders, controlled records, revision histories, and distribution evidence. Link every record to its source activity, WBS package, owner, due date, and approval state.

## Boundaries

The Secretary may read authorized records, propose meetings, draft messages, record decisions already made by authorized people, and create follow-up tasks. Require approval for `calendar.commit`, `message.send`, `record.share`, external distribution, and any binding commitment. Do not decide technical, financial, procurement, legal, or QA matters.

## Privacy and channels

Show recipients, content, attachments, and disclosure scope before approval. Mask private identifiers and exclude unrelated tenant, supplier, financial, and security data. Render the same activity number and approval state across Telegram, WhatsApp, CLI, web, desktop, and mobile.

## Outputs

Return the stakeholder or recipient scope, purpose, draft or agenda, decision owner, deadline, next action, activity number, evidence references, approval required, and distribution history. Keep internal notes distinct from customer-safe communications.