For Agents · MCP

Your task.
The right skill.

The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.

No local installationNo M11 loginRead-only

Broad task

Load 5–10 and go

SEO, Sales, Agents or another broad area → one bundle call → work.

MCP endpoint: https://skills.m11.ch/mcp

Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.

Task Packs

Marketing Foundation

Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.

Marketing Launch

Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.

Agent Audit Essentials

Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.

Conversion and Activation Review

Review the journey from landing page and lead capture through registration, first value and transparent upgrades.

Campaign Content and Brand Review

Plan a campaign, draft its channel content and review the work against actual brand guidance.

Content and Launch Planning

Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.

Customer, Market and Community Research

Understand customer needs, compare competitors and plan a community around real member value.

Lead Magnet to Lifecycle Nurture

Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.

API Contract and Observability

Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.

Data Analysis Foundation

Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.

B2B Outreach Foundation

Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.

Choose an area

01 · Category

What the MCP returns at this step

109 · Business · Operations Design

Organization Design Register

Org structure register: department, type, parent, head, location, approved against actual headcount, annual budget, cost centre code and establishment date. Use for org design.

businessoperations-designsickn33organization-design

Sickn33 — Organization Design Register · Original SKILL.md

---
name: organization-design
description: 'Org structure register: department, type, parent, head, location, approved against actual headcount, annual budget, cost centre code and establishment date. Use for org design.'
category: business
risk: safe
source: self
source_type: self
date_added: "2026-09-26"
author: WHOISABHISHEKADHIKARI
tags: [sme, business, operations, database, csv, notion, sql, foundation]
tools: []
source_repo: WHOISABHISHEKADHIKARI/sme-ops-system-builder
---

# Organization Design

**What it is:** Org structure & planning.

## Overview

Works out the smallest useful **Organization Design** setup for the business in front of it, then
builds it only when asked. The default output is a short recommendation, not a
spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on
request, from one field list so they cannot drift apart.

Layer: Layer 1: Foundation. Fits: Starter stage. Table code: n/a.

## When to Use This Skill

- org chart template
- department structure planner
- headcount and budget planning
- org design spreadsheet

Also use it when the user says "org structure & planning", or describes the same process happening in a
spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces
empty templates only - it never holds or processes real employee or customer data.

## How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

### Step 1 - Identify intent

Read the request and pick the intent before asking anything.

- "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
- "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
- "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
- "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

> **Q:** How many departments does the company have?

### Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a
time, and stop as soon as the remaining answers would not change the output.

- **Shape** - How many departments? / Any business units? / Remote or on-site?
- **Ownership** - Who heads each one? / Reporting lines? / Matrix or simple?
- **Numbers** - Headcount per team? / Budget per team? / Cost centres used?
- **Current process** - Is the org chart current? / Drawn where? / What is stale?
- **Outcome** - What do you need it for? / Planning, hiring or budget?

Never invent an answer. If the user does not know, record it as unknown and carry on.

### Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless
they ask, and it never carries a value the user did not give.

```yaml
module: organization-design
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Shape": null
  "Ownership": null
  "Numbers": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
```

### Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

**Recommended approach:** Model departments as data with a head and an owner, not as a drawing. The chart becomes a view, not the source.

**Why this one:** Org charts rot because they are maintained as pictures. Storing departments as rows with an owner and a headcount keeps the chart regenerable.

**Workflow:** Departments → Owners → Headcount and budget → Chart view → Quarterly refresh

### Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the
requested artifacts. For machine-readable text, keep prose outside the data; for files,
provide a usable link. Report material validation failures or limitations separately.

**A selected Notion output is rendered by `notion-manual-import`, so route the
Notion step there.** When the user selects Notion, hand that step to
](https://github.com/sickn33/agentic-awesome-skills/blob/main/skills/notion-manual-import/SKILL.md): it holds the CSV, the property
mapping, the import steps and the verification checklist, and it renders the Field
Reference below instead of defining a table of its own. Do not restate the mapping
here and do not improvise the import steps. Manual CSV and mapping outputs need no
connection. For requested workspace changes, follow the shared contract: verify actual
tool access and the target before writing. A user saying "connected" is not tool evidence.
Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the
text correctly. A CSV is not an `.xlsx` workbook; create `.xlsx` only when the user
requests a workbook.
A CSV carries no types, so after it, name the columns
that need a number, date or currency format applied.

```csv
Department Name,Approved Headcount,Budget (Annual),Cost Center Code,Department Head,Department Type,Dept ID,Established Date,Headcount,Location,Notes,Parent Department,Status
Delivery,14,4800000.00,CC-100,Sneha Iyer,Revenue,,2026-01-15,12,Bengaluru,Drafted after the February leadership offsite; spans are still contested.,Operations,Live
```

```sql
CREATE TABLE organization_design (
  department_name VARCHAR(255),
  approved_headcount NUMERIC NOT NULL,
  budget_annual NUMERIC(14,2) NOT NULL,
  cost_center_code VARCHAR(255),
  department_head VARCHAR(255),
  department_type VARCHAR(100) NOT NULL,
  dept_id SERIAL PRIMARY KEY,
  established_date DATE NOT NULL,
  headcount NUMERIC NOT NULL,
  location VARCHAR(255),
  notes TEXT,
  parent_department VARCHAR(255),
  status VARCHAR(100) NOT NULL,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_organization_design_status ON organization_design (status);
```

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Organization Design",
  "type": "object",
  "additionalProperties": false,
  "properties": {
      "Department Name": { "type": "string" },
      "Approved Headcount": { "type": "number" },
      "Budget (Annual)": { "type": "number" },
      "Cost Center Code": { "type": "string" },
      "Department Head": { "type": "string" },
      "Department Type": { "type": "string" },
      "Dept ID": { "type": "integer" },
      "Established Date": { "type": "string", "format": "date" },
      "Headcount": { "type": "number" },
      "Location": { "type": "string" },
      "Notes": { "type": "string" },
      "Parent Department": { "type": "string" },
      "Status": { "type": "string" }
  },
  "required": [
      "Approved Headcount",
      "Budget (Annual)",
      "Department Type",
      "Established Date",
      "Headcount",
      "Status"
  ]
}
```

```markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Department Name | Title | Use as the database title |
| Approved Headcount | Number | Convert to Number |
| Budget (Annual) | Number (format: currency) | Convert to Number, set format to Currency |
| Cost Center Code | Text | Leave as Text |
| Department Head | Text | Leave as Text |
| Department Type | Select (add options after import) | Convert to Select, add options: "Revenue", "Delivery", "Support", "Finance", "People", "Admin", "Engineering" |
| Dept ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
| Established Date | Date | Convert to Date |
| Headcount | Number | Convert to Number |
| Location | Text | Leave as Text |
| Notes | Text | Leave as Text |
| Parent Department | Text | Leave as Text |
| Status | Select (add options after import) | Convert to Select, add options: "Proposed", "Under Review", "Approved", "Implementing", "Live", "Superseded" |
```

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays `currency`, dates stay `date`,
and anything pointing at another table stays `relation`.

## Field Reference

| # | Field | Type | SQL | JSON Schema | Notion | CSV example |
|---:|---|---|---|---|---|---|
| 1 | Department Name | `text` | `VARCHAR(255)` | `string` | Text | `Delivery` |
| 2 | Approved Headcount | `number` | `NUMERIC` | `number` | Number | `14` |
| 3 | Budget (Annual) | `currency` | `NUMERIC(14,2)` | `number` | Number (format: currency) | `4800000.00` |
| 4 | Cost Center Code | `text` | `VARCHAR(255)` | `string` | Text | `CC-100` |
| 5 | Department Head | `text` | `VARCHAR(255)` | `string` | Text | `Sneha Iyer` |
| 6 | Department Type | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Revenue` |
| 7 | Dept ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text (preserve source ID) | `(blank)` |
| 8 | Established Date | `date` | `DATE` | `string, format: date` | Date | `2026-01-15` |
| 9 | Headcount | `number` | `NUMERIC` | `number` | Number | `12` |
| 10 | Location | `text` | `VARCHAR(255)` | `string` | Text | `Bengaluru` |
| 11 | Notes | `long_text` | `TEXT` | `string` | Text | `Drafted after the February leadership offsite; spans are still contested.` |
| 12 | Parent Department | `text` | `VARCHAR(255)` | `string` | Text | `Operations` |
| 13 | Status | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Live` |

## Select Options

**Department Type**

```
Revenue | Delivery | Support | Finance | People | Admin | Engineering
```
**Status**

```
Proposed | Under Review | Approved | Implementing | Live | Superseded
```

## Relations

Link fields: none

## Examples

**Prompt**

```
We are 14 people across sales and delivery and want to plan hiring.
```

**Context first** - one question per message, nothing already answered:

> **Q:** How many departments?
> **A:** Sales, delivery and finance.
>
> **Q:** Do you have cost centres?
> **A:** No.
>
> **Q:** What is it for?
> **A:** Hiring plan and budget.

**Recommended next step** - offered, not built:

> Model departments as data with a head and an owner, not as a drawing. The chart becomes a view, not the source.
>
> Workflow: Departments → Owners → Headcount and budget → Chart view → Quarterly refresh
>
> Want the CSV, SQL, JSON Schema and Notion mapping for this?

## Best Practices

- Build when requested; recommend and offer a build for advice-only requests.
- One question per message. A batched intake reads as a form and gets guessed at.
- Keep display names identical across CSV and JSON; document normalized SQL identifiers.
- Use `relation` for anything that points at another table, `text` only for free text.
- Money fields are `currency`, never `text`. Dates are `date`, never free text.
- If the user requests an example row, keep it obviously fake so nobody imports it as real data.

## Limitations

- Empty template only. It does not compute payroll, tax, leave balances or KPIs.
- Notion relations need both databases imported before the link column resolves.
- Select options are a starting set. Rename them to match how the business talks.
- No automation, reminders or sync. Those need the integration layer.
- Does not handle detailed reporting lines or dotted-line matrix structures.
- Legal, tax and HR review is still required before this drives real decisions.

## Security & Safety Notes

- Never fill in real names, salaries, medical or banking data. Placeholders only.
- Label example rows as synthetic, and keep bank details masked.
- Local reads, generation commands, and validation are part of a requested artifact build.
  External writes, messages, provisioning, and publication require authorization for that
  action and target; existing explicit authorization does not need to be repeated.
- If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what
  the requested review needs; keep generated templates empty. Do not claim deletion
  from the conversation or service storage.
- Privacy, legal and disciplinary cases need a qualified human reviewer before anything
  is acted on.

## Common Pitfalls

- **Problem:** a static mapping is described as a completed workspace build.
  **Solution:** deliver manual mappings without a connection; claim a live change only
  after the authorized tool operation succeeds.
- **Problem:** asked all six questions in one message.
  **Solution:** ask one, wait, and drop any the first answer already covered.
- **Problem:** built a full system when one table was asked for.
  **Solution:** build what was requested; mention the parent skill separately.
- **Problem:** all four artifacts drift apart.
  **Solution:** derive all four from the field list in this file, never by hand.
- **Problem:** Notion import shows every column as Text.
  **Solution:** that is expected. Apply the property mapping table once, after import.

## Related Skills

- ](https://github.com/sickn33/agentic-awesome-skills/blob/main/CATALOG.md) - find the relevant module, then read its skill.
- @people-directory - the employee master record most modules link to.
- ](https://github.com/sickn33/agentic-awesome-skills/blob/main/skills/notification-reminder-hub/SKILL.md) - turns due dates in this module into reminders.

## Reusable Prompt

```
I want to set up org structure & planning for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.
```

When to use

Org structure register: department, type, parent, head, location, approved against actual headcount, annual budget, cost centre code and establishment date. Use for org design.

What you get

Complete original guidance with source attribution and declared limits.

How it works

Use the supplied task context and evidence to plan or review the workflow.

Requirements

User-provided, authorized business context and a named decision owner.

Delivery and review notes

Brief danger screen only; this source can include command, API or workflow examples. The catalog does not run code, access accounts, install tools, upload data, send messages, or make external changes.

Starting prompt

Use Sickn33 — Organization Design Register for [TASK]. Work from user-provided, authorized context; identify unknowns and assumptions. Do not connect services, install tools, access credentials, send messages, upload files, or make external changes from this text alone.

Not for

Automatic execution, account or credential access, scraping, uploads, sending, publishing, financial decisions, or external record changes.

What M11 added

M11 added German routing, source attribution, integrity tracking and an explicit no-execution boundary. Original attribution: WHOISABHISHEKADHIKARI. Brief danger screen only; this source can include command, API or workflow examples. The catalog does not run code, access accounts, install tools, upload data, send messages, or make external changes.

Original authorship remains with sickn33/agentic-awesome-skills · Original source ↗

Original license & copyright

MIT License

Copyright (c) 2026 Antigravity User

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Source SHA-256: 3186d4df123dd5bd81013cb8ebc837dc0b30a89061394b988668181690048e4a
Snapshot checked: 2026-10-05T00:00:00.000Z

Find a skill.Get to work.

All skills

Multi-Agent Orchestration

AI Context Window Audit

AI Agent Architecture Audit

AI Skill Discovery

Lead Magnet Strategy

Ideal Customer Profile

Go-to-Market Strategy

Marketing Campaign Ideas

Product Growth Loops

Competitor Analysis

North Star Metric

Product Positioning

Product Vision

Go-to-Market Motion Selection

Customer Feedback and JTBD Analysis

PESTLE Market Environment Analysis

Customer Journey Mapping

Ansoff Growth Options

Data Analysis Validation

Dataset Profiling

Statistical Analysis Guidance

Programmatic SEO Planning

Landing Page and Form Conversion Review

Paywall and Upgrade Planning

Signup and Registration Review

User Onboarding and Activation

Popup and Modal Planning

Email Sequence Copy and Flow

Marketing Campaign Planning

Marketing Content Drafting

Brand Voice and Content Review

Marketing Performance Reporting

Sales Company Research

Company and Contact Enrichment

Website Information Architecture

Content Strategy and Editorial Roadmap

Product Launch Planning

Customer Research and Voice of Customer

Community Growth and Member Experience

Competitor Research Profiles

Roadmap and Release Communication

Lifecycle Email Sequences

API Contracts and Interface Design

Observability and Instrumentation Planning

Agent Context and Session Handoff

Product Discovery Sprint

Deal Quality Scoring

Enrichment Waterfall Design

Customer Retention Playbook

Sales Coaching Practice

Revenue Cohort Analysis

Intent Signal Scoring

Customer Identity Matching

Segment Activation Planning

Sales Call Review

Retention Dashboard Design

Sales Coaching Competencies

Offer Delivery Design

Offer Value Communication

Service Productization

Conversion Hypothesis Prioritization

Braze Engagement Guidance

Brand Voice Guide Design

Content Pipeline Orchestration

Website Brand Profile

Buyer Objection Clarification

Klaviyo Integration Guidance

Offer Bonus Planning

Klaviyo Marketing Review

Cross-Platform Advertising Review

Expertise Business Model

LinkedIn Advertising Guidance

TikTok Advertising Guidance

Evidence Research Brief

Cinematic Video Prompts

Visual Prompt Model Adaptation

Visual Prompt Diagnostics

Short Film Development

Find a skill.
Get to work.