setup skill
Initializes a four-layer workplace memory file and orients the user to the two-plugin architecture for professional intelligence.
- GitHub stars
- 37
- Files
- 3
- Last commit
- Mar 26, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the setup skill do?
setup initializes a four-layer workplace memory file and orients the user to the two-plugin architecture for professional intelligence.
Summary generated from the skill's SKILL.md.
About the setup skill
Setting up a structured workplace memory for professional intelligence is what this skill enables. It is designed for users who need to establish an agentic office environment by creating a foundational work.local.md file. The process involves copying a template from the CLAUDE_PLUGIN_ROOT directory and guiding the user through an interactive configuration of four distinct layers: personal details, team members, active projects, and organizational nuances like acronyms or unwritten rules.
Agents should load this skill to initialize a workspace or orient a user to the two-plugin architecture. It distinguishes between the official productivity plugin, which manages basic tasks and dashboards, and the agentic office plugin, which provides specialized intelligence skills like meeting intelligence and executive briefs. The skill also allows for the integration of domain agents from other departments such as finance or HR by updating the agent_integrations section of the memory file. Once configured, the agent verifies the setup by generating a test digest to ensure the data is specific enough for high-quality output.
What an agent can do with it
- 1Initialize workplace memoryCreate a new work.local.md file from a template to start building a professional intelligence foundation.
- 2Configure organizational contextBuild out the four-layer memory structure including personal, team, project, and organizational details.
- 3Integrate domain agentsConnect specialized agents from finance, sales, or HR to the central dashboard and digest.
- 4Explain plugin architectureHelp a user understand the difference between the official productivity plugin and the agentic office plugin.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the setup skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the setup skill in Plugin
/plugin marketplace add panaversity/agentfactory-business-plugins /plugin install agentic-office@agentfactory-business
Install the setup skill in Claude Code
~/.claude/skills/setup/SKILL.md
$ npx degit panaversity/agentfactory-business-plugins/agentic-office/skills/setup ~/.claude/skills/setupInstall the setup skill in Claude Code (project)
.claude/skills/setup/SKILL.md
$ npx degit panaversity/agentfactory-business-plugins/agentic-office/skills/setup .claude/skills/setupInstall the setup skill in Codex
~/.agents/skills/setup/SKILL.md
$ npx degit panaversity/agentfactory-business-plugins/agentic-office/skills/setup ~/.agents/skills/setupInstall the setup skill in Gemini CLI
~/.gemini/skills/setup/SKILL.md
$ npx degit panaversity/agentfactory-business-plugins/agentic-office/skills/setup ~/.gemini/skills/setupInstall the setup skill in Claude.ai
npx degit panaversity/agentfactory-business-plugins/agentic-office/skills/setup setup && zip -r setup.zip setup # claude.ai → Customize → Skills → + → Create skill → Upload a skill → setup.zip
SKILL.md
View on GitHubAGENTIC OFFICE SETUP
This skill creates your work.local.md workplace memory file from the
bundled template and orients you to the two-plugin architecture.
STEP 1 — LOAD CONTEXT
Read work.local.md in the current working directory.
If it already exists, skip to STEP 4 (orientation only).
STEP 2 — CREATE WORK.LOCAL.MD
Copy the template from ${CLAUDE_PLUGIN_ROOT}/work.local.md.template
to work.local.md in the current working directory.
Tell the user:
I have created work.local.md from the Agentic Office template.
This file is your four-layer workplace memory — the foundation
for all professional intelligence features.
STEP 3 — GUIDED CONFIGURATION
Walk the user through filling in each layer interactively:
Layer 1 — Personal: Ask for: name, role, working style, decision-making approach, current focus (top 1-3 priorities), working hours, communication preference.
Layer 2 — Team (People): Ask: "Who are the 5-8 people you interact with most? For each, I need: name, role, how they prefer to receive information, and what they are working on right now."
Layer 3 — Projects: Ask: "What are your active projects? For each: name, any internal codename, current status, priority (P1/P2/P3), and what is happening right now."
Layer 4 — Organisational: Ask: "What internal terms, acronyms, or codenames would confuse an outsider? What are your recurring meetings? Any unwritten rules that every colleague knows but nobody writes down?"
After each layer, write the entries to work.local.md and confirm.
STEP 4 — ORIENTATION MESSAGE
Deliver this orientation:
Your Agentic Office uses two plugins working together:
OFFICIAL PRODUCTIVITY PLUGIN (Anthropic)
/productivity:start — Initialise TASKS.md + CLAUDE.md + dashboard
/productivity:update — Sync from external tools, triage stale items
Provides: Basic task CRUD, two-tier memory, visual dashboard
AGENTIC OFFICE PLUGIN (Panaversity)
9 professional intelligence skills:
workplace-context — Four-layer workplace memory (work.local.md)
workplace-search — Cross-context search across all memory layers
task-intelligence — Brain dump capture, P1/P2/P3 prioritisation
delegation — Delegation quality standard + handoff comms
digest — Daily morning briefing assembly
meeting-intelligence — Three-phase meeting model (before/during/after)
progress-tracker — RAG status, milestones, blocker classification
context-loader — Cross-domain context injection
executive-brief — Situation briefs (pre-meeting, decision, person)
4 persistent agents:
chief-of-staff — Orchestration: digest delivery, threshold alerts
memory-keeper — work.local.md maintenance, trigger-based updates
meeting-intelligence-agent — Calendar-triggered prep and post-meeting synthesis
work-tracker — Delegation lifecycle, overdue protocol
The official plugin handles task and memory CRUD.
The agentic office adds professional intelligence on top.
Try: "Give me my daily digest" or "Brain dump my priorities"
STEP 5 — CONFIGURE AGENT INTEGRATIONS
Ask: "Do you have any domain agents deployed from other chapters (finance, sales, HR, operations, supply chain)? I can configure the agent integration section so your digest and dashboard pull from those domain agents too."
If yes: update the agent_integrations section of work.local.md
with the appropriate feeds.
STEP 6 — VERIFY
Run a quick test: generate a brief digest using the data just entered. If the output feels generic, prompt the user to add more specificity to terminology and unwritten_rules sections.
NEVER DO THESE
- NEVER skip the orientation message — users must understand the two-plugin architecture before using any skills
- NEVER overwrite an existing work.local.md without asking first
- NEVER leave the agent_integrations section empty without asking whether domain agents are deployed
Files in this skill
3setup skill questions
How do I install the setup skill in Claude Code?
Run npx degit panaversity/agentfactory-business-plugins/agentic-office/skills/setup ~/.claude/skills/setup. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the setup skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What does the setup skill actually create?
It creates a work.local.md file which serves as a four-layer workplace memory foundation for professional intelligence features.
How does the Agentic Office architecture work?
It uses a two-plugin system: an Official Productivity Plugin for task CRUD and a dashboard, and the Agentic Office Plugin for professional intelligence skills like workplace-context and task-intelligence.
Can I use this skill to set up the official productivity plugin?
No, this skill is not for official productivity plugin setup; you should use the /productivity:start command instead.