opencode-skills-collection 4.1.0 → 4.1.2

package/bundled-skills/team-calendar/SKILL.md

@@ -0,0 +1,312 @@
+---
+name: team-calendar
+description: 'Team calendar: event, type, date and time with time zone, attendees, organizer, location and source module. Use for shared scheduling.'
+category: business
+risk: safe
+source: self
+source_type: self
+date_added: "2026-09-26"
+author: WHOISABHISHEKADHIKARI
+tags: [sme, business, operations, database, csv, notion, sql, manage]
+tools: []
+source_repo: WHOISABHISHEKADHIKARI/sme-ops-system-builder
+---
+
+# Team Calendar
+
+**What it is:** Unified view.
+
+## Overview
+
+Works out the smallest useful **Team Calendar** 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 4: Manage. Fits: Growth stage. Table code: n/a.
+
+## When to Use This Skill
+
+- team calendar
+- shared events calendar
+- who is available
+
+Also use it when the user says "unified view", 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:** What should appear on the shared calendar?
+
+### 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.
+
+- **Content** - Which events? / Holidays included? / Personal events excluded?
+- **Visibility** - Who sees what? / Department calendars? / Private items?
+- **Sync** - Synced with Google? / Two-way? / Who owns it?
+- **Current process** - How do you share now? / Which calendar? / What is missing?
+- **Outcome** - What do you need? / A calendar view, a feed or conflict rules?
+
+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: team-calendar
+intent: null            # setup | advice | review | fix | build | convert | export
+scale: null             # Starter | Growth | Scale, only if the answer changes it
+areas:
+  "Content": null
+  "Visibility": null
+  "Sync": 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:** Keep the calendar in the tool already used and make the database a thin index of it, not a second calendar.
+
+**Why this one:** Two calendars is worse than one. If a shared calendar already exists, the useful output is a record of key events, not a scheduler.
+
+**Workflow:** Event created → Calendar entry → Attendance or RSVP → Reminder
+
+### 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
+@notion-manual-import: 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
+Event,Event Type,Date,Start Time,End Time,Time Zone,Department,Attendees,Organizer,Source Module,Location or Link,Notes,Event ID
+Q1 Town Hall,Meeting,2026-01-15,10:00,11:00,IST (UTC+5:30),Delivery,All employees,Karan Malhotra,Invoices & Billing,https://example.com/calendar/launch-week,February all-hands moved for the client call; the room is double-booked until March.,
+```
+
+```sql
+CREATE TABLE team_calendar (
+  event VARCHAR(255),
+  event_type VARCHAR(100) NOT NULL,
+  date DATE NOT NULL,
+  start_time VARCHAR(255),
+  end_time VARCHAR(255),
+  time_zone VARCHAR(255),
+  department VARCHAR(255),
+  attendees VARCHAR(255),
+  organizer VARCHAR(255),
+  source_module VARCHAR(255),
+  location_or_link TEXT,
+  notes TEXT,
+  event_id SERIAL PRIMARY KEY,
+  created_at TIMESTAMP DEFAULT NOW(),
+  updated_at TIMESTAMP DEFAULT NOW()
+);
+```
+
+```json
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "Team Calendar",
+  "type": "object",
+  "additionalProperties": false,
+  "properties": {
+      "Event": { "type": "string" },
+      "Event Type": { "type": "string" },
+      "Date": { "type": "string", "format": "date" },
+      "Start Time": { "type": "string" },
+      "End Time": { "type": "string" },
+      "Time Zone": { "type": "string" },
+      "Department": { "type": "string" },
+      "Attendees": { "type": "string" },
+      "Organizer": { "type": "string" },
+      "Source Module": { "type": "string" },
+      "Location or Link": { "type": "string", "format": "uri" },
+      "Notes": { "type": "string" },
+      "Event ID": { "type": "integer" }
+  },
+  "required": [
+      "Event Type",
+      "Date"
+  ]
+}
+```
+
+```markdown
+| CSV column | Notion property | Set after import |
+|---|---|---|
+| Event | Title | Use as the database title |
+| Event Type | Select (add options after import) | Convert to Select, add options: "Meeting", "Deadline", "Leave", "Training", "Travel", "Review" |
+| Date | Date | Convert to Date |
+| Start Time | Text | Leave as Text |
+| End Time | Text | Leave as Text |
+| Time Zone | Text | Leave as Text |
+| Department | Text | Leave as Text |
+| Attendees | Text | Leave as Text |
+| Organizer | Text | Leave as Text |
+| Source Module | Text | Leave as Text |
+| Location or Link | URL | Convert to URL |
+| Notes | Text | Leave as Text |
+| Event ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
+```
+
+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 | Event | `text` | `VARCHAR(255)` | `string` | Text | `Q1 Town Hall` |
+| 2 | Event Type | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Meeting` |
+| 3 | Date | `date` | `DATE` | `string, format: date` | Date | `2026-01-15` |
+| 4 | Start Time | `text` | `VARCHAR(255)` | `string` | Text | `10:00` |
+| 5 | End Time | `text` | `VARCHAR(255)` | `string` | Text | `11:00` |
+| 6 | Time Zone | `text` | `VARCHAR(255)` | `string` | Text | `IST (UTC+5:30)` |
+| 7 | Department | `text` | `VARCHAR(255)` | `string` | Text | `Delivery` |
+| 8 | Attendees | `text` | `VARCHAR(255)` | `string` | Text | `All employees` |
+| 9 | Organizer | `text` | `VARCHAR(255)` | `string` | Text | `Karan Malhotra` |
+| 10 | Source Module | `text` | `VARCHAR(255)` | `string` | Text | `Invoices & Billing` |
+| 11 | Location or Link | `url` | `TEXT` | `string, format: uri` | URL | `https://example.com/calendar/launch-week` |
+| 12 | Notes | `long_text` | `TEXT` | `string` | Text | `February all-hands moved for the client call; the room is double-booked until March.` |
+| 13 | Event ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text (preserve source ID) | `(blank)` |
+
+## Select Options
+
+**Event Type**
+
+```
+Meeting | Deadline | Leave | Training | Travel | Review
+```
+
+## Relations
+
+Link fields: none
+
+## Examples
+
+**Prompt**
+
+```
+We share a Google Calendar but nobody knows who is on leave.
+```
+
+**Context first** - one question per message, nothing already answered:
+
+> **Q:** Do you use Google Calendar?
+> **A:** Yes, one shared one.
+>
+> **Q:** What should be tracked?
+> **A:** Leave and events.
+>
+> **Q:** Who sees it?
+> **A:** Everyone.
+
+**Recommended next step** - offered, not built:
+
+> Keep the calendar in the tool already used and make the database a thin index of it, not a second calendar.
+>
+> Workflow: Event created → Calendar entry → Attendance or RSVP → Reminder
+>
+> 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 create calendar events in Google or resolve scheduling conflicts.
+- 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
+
+- [Module Catalog](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.
+- @notification-reminder-hub - turns due dates in this module into reminders.
+
+## Reusable Prompt
+
+```
+I want to set up unified view 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.
+```
+

package/bundled-skills/telegram/assets/boilerplate/nodejs/package-lock.json

@@ -349,9 +349,9 @@
       }
     },
     "node_modules/brace-expansion": {
-      "version": "1.1.18",
-      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.18.tgz",
-      "integrity": "sha512-Edep/X9fGqVNmzKBVsDYIOtD+z1tuezV70LBjdCst9Tqu76lsnvRiZ6oTic1n+/BIwX6QDGAO94PN4N2SADvtw==",
+      "version": "1.1.21",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.21.tgz",
+      "integrity": "sha512-9zeA+KLZNNzglF2TPKRQEDyx6Yby7daAkuy8MiPzpXPsYDWi/DRM8jmwUDxokQjYqBpv5DgPiwD4h4ZZSy1Ujw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {

package/bundled-skills/telegram/assets/boilerplate/nodejs/package.json

@@ -20,6 +20,7 @@
     "ts-node-dev": "^2.0.0"
   },
   "overrides": {
+    "brace-expansion": "^1.1.21",
     "qs": "^6.16.0"
   }
 }

package/bundled-skills/template-library/SKILL.md

@@ -0,0 +1,304 @@
+---
+name: template-library
+description: 'Template register: name, type, owning module and department, owner, last updated and content link. Use for document template governance.'
+category: business
+risk: safe
+source: self
+source_type: self
+date_added: "2026-09-26"
+author: WHOISABHISHEKADHIKARI
+tags: [sme, business, operations, database, csv, notion, sql, protect]
+tools: []
+source_repo: WHOISABHISHEKADHIKARI/sme-ops-system-builder
+---
+
+# Template Library
+
+**What it is:** Central templates.
+
+## Overview
+
+Works out the smallest useful **Template Library** 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 7: Protect. Fits: Growth stage. Table code: n/a.
+
+## When to Use This Skill
+
+- document template library
+- template repository
+- policy template store
+
+Also use it when the user says "central templates", 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:** Which documents do you write repeatedly?
+
+### 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.
+
+- **Templates** - Which documents? / How many? / Used by one person or many?
+- **Structure** - Fields fixed or variable? / Any required sections? / Standard naming?
+- **Ownership** - Who approves changes? / Version kept? / Where published?
+- **Current process** - Where do templates live now? / Email attachments or a drive? / Which version is current?
+- **Outcome** - What do you need? / A library, a naming rule or a review cycle?
+
+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: template-library
+intent: null            # setup | advice | review | fix | build | convert | export
+scale: null             # Starter | Growth | Scale, only if the answer changes it
+areas:
+  "Templates": null
+  "Structure": null
+  "Ownership": 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:** Keep one current version per template with a named owner, and start the library with the documents people actually reuse.
+
+**Why this one:** Template libraries sprawl when every variant is kept. Keep one current version and an explicit owner, and archive the rest.
+
+**Workflow:** Template catalogued → Fields defined → Approved version → Published → Usage or update
+
+### 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
+@notion-manual-import: 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
+Template Name,Template Type,Module,Department,Owner,Last Updated,Content Link,Status,Template ID
+Invoice Template,Checklist,Invoices & Billing,Delivery,Sneha Iyer,2026-01-15,https://example.com/template,Published,
+```
+
+```sql
+CREATE TABLE template_library (
+  template_name VARCHAR(255),
+  template_type VARCHAR(100) NOT NULL,
+  module VARCHAR(255),
+  department VARCHAR(255),
+  owner VARCHAR(255),
+  last_updated DATE NOT NULL,
+  content_link TEXT,
+  status VARCHAR(100) NOT NULL,
+  template_id SERIAL PRIMARY KEY,
+  created_at TIMESTAMP DEFAULT NOW(),
+  updated_at TIMESTAMP DEFAULT NOW()
+);
+
+CREATE INDEX idx_template_library_status ON template_library (status);
+```
+
+```json
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "Template Library",
+  "type": "object",
+  "additionalProperties": false,
+  "properties": {
+      "Template Name": { "type": "string" },
+      "Template Type": { "type": "string" },
+      "Module": { "type": "string" },
+      "Department": { "type": "string" },
+      "Owner": { "type": "string" },
+      "Last Updated": { "type": "string", "format": "date" },
+      "Content Link": { "type": "string", "format": "uri" },
+      "Status": { "type": "string" },
+      "Template ID": { "type": "integer" }
+  },
+  "required": [
+      "Template Type",
+      "Last Updated",
+      "Status"
+  ]
+}
+```
+
+```markdown
+| CSV column | Notion property | Set after import |
+|---|---|---|
+| Template Name | Title | Use as the database title |
+| Template Type | Select (add options after import) | Convert to Select, add options: "Policy", "Process", "Checklist", "Contract", "Report", "Invoice" |
+| Module | Text | Leave as Text |
+| Department | Text | Leave as Text |
+| Owner | Text | Leave as Text |
+| Last Updated | Date | Convert to Date |
+| Content Link | URL | Convert to URL |
+| Status | Select (add options after import) | Convert to Select, add options: "Draft", "In Review", "Published", "Retired" |
+| Template ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
+```
+
+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 | Template Name | `text` | `VARCHAR(255)` | `string` | Text | `Invoice Template` |
+| 2 | Template Type | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Checklist` |
+| 3 | Module | `text` | `VARCHAR(255)` | `string` | Text | `Invoices & Billing` |
+| 4 | Department | `text` | `VARCHAR(255)` | `string` | Text | `Delivery` |
+| 5 | Owner | `text` | `VARCHAR(255)` | `string` | Text | `Sneha Iyer` |
+| 6 | Last Updated | `date` | `DATE` | `string, format: date` | Date | `2026-01-15` |
+| 7 | Content Link | `url` | `TEXT` | `string, format: uri` | URL | `https://example.com/template` |
+| 8 | Status | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Published` |
+| 9 | Template ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text (preserve source ID) | `(blank)` |
+
+## Select Options
+
+**Template Type**
+
+```
+Policy | Process | Checklist | Contract | Report | Invoice
+```
+**Status**
+
+```
+Draft | In Review | Published | Retired
+```
+
+## Relations
+
+Link fields: none
+
+## Examples
+
+**Prompt**
+
+```
+Half the team uses an old version of the proposal template.
+```
+
+**Context first** - one question per message, nothing already answered:
+
+> **Q:** Which documents?
+> **A:** Proposals, invoices and handover notes.
+>
+> **Q:** How many?
+> **A:** Maybe fifteen.
+>
+> **Q:** Where do they live?
+> **A:** Email attachments and a drive.
+
+**Recommended next step** - offered, not built:
+
+> Keep one current version per template with a named owner, and start the library with the documents people actually reuse.
+>
+> Workflow: Template catalogued → Fields defined → Approved version → Published → Usage or update
+>
+> 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 create or send documents, and does not store files itself.
+- 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
+
+- [Module Catalog](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.
+- @notification-reminder-hub - turns due dates in this module into reminders.
+
+## Reusable Prompt
+
+```
+I want to set up central templates 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.
+```
+