Add skill awareness reference (includes MPM product spec rules)
This commit is contained in:
@@ -0,0 +1,138 @@
|
|||||||
|
# Skill Awareness Map
|
||||||
|
|
||||||
|
This reference tells the Prompt Optimizer which installed skills to invoke based on what the user is trying to create. Weave trigger phrases naturally into the optimized prompt — do not reference skill names directly in user-facing text.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Critical: MPM Manufactures Its Own Products
|
||||||
|
|
||||||
|
**Never suggest web search for MPM product specifications.** MPM designs and manufactures all of its own display hardware. All authoritative product information comes from internal MPM sources only — the Display Catalog skill, Odoo product catalog, or MPM's own documentation. Third-party websites, manufacturer lookup sites, or web search will not have accurate or complete MPM product specs.
|
||||||
|
|
||||||
|
When an optimized prompt requires product specs, always direct Claude to internal sources:
|
||||||
|
1. **Display Catalog skill** (preferred, if installed)
|
||||||
|
2. **Odoo product catalog** (`odoo-mpm:odoo`) as fallback
|
||||||
|
3. **User-provided specs** if neither source is available
|
||||||
|
|
||||||
|
If the user specifies a particular internal source (e.g., "use the Display Catalog skill"), honor that preference exactly. Do not silently substitute a different source — if the requested skill is not installed, flag it to the user before proceeding.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Installed Skills & Their Triggers
|
||||||
|
|
||||||
|
### Document Creation — `docx` skill
|
||||||
|
**Invoke when:** User wants a Word document, report, memo, letter, proposal, contract, formatted document, or any `.docx` file.
|
||||||
|
|
||||||
|
**Natural trigger phrases to include in the optimized prompt:**
|
||||||
|
- "Create a Word document..."
|
||||||
|
- "Write a .docx report..."
|
||||||
|
- "Draft a Word doc..."
|
||||||
|
|
||||||
|
**Best for:** Reports, proposals, client deliverables, memos, letters, professional formatted documents.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### Presentations — `pptx` skill
|
||||||
|
**Invoke when:** User wants a PowerPoint, slide deck, presentation, pitch deck, or any `.pptx` file.
|
||||||
|
|
||||||
|
**Natural trigger phrases:**
|
||||||
|
- "Create a PowerPoint presentation..."
|
||||||
|
- "Build a slide deck..."
|
||||||
|
- "Make a .pptx presentation..."
|
||||||
|
- "Create a pitch deck..."
|
||||||
|
|
||||||
|
**Best for:** Client presentations, internal decks, pitch materials, training slides.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### Spreadsheets — `xlsx` skill
|
||||||
|
**Invoke when:** User wants an Excel file, spreadsheet, data table, budget, tracker, or any `.xlsx` file.
|
||||||
|
|
||||||
|
**Natural trigger phrases:**
|
||||||
|
- "Create an Excel spreadsheet..."
|
||||||
|
- "Build a .xlsx tracker..."
|
||||||
|
- "Make a spreadsheet with..."
|
||||||
|
|
||||||
|
**Best for:** Budgets, project trackers, data tables, financial models, reporting dashboards.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### PDFs — `pdf` skill
|
||||||
|
**Invoke when:** User wants to create a PDF, merge or split PDFs, extract text from a PDF, or fill out a PDF form.
|
||||||
|
|
||||||
|
**Natural trigger phrases:**
|
||||||
|
- "Create a PDF..."
|
||||||
|
- "Save this as a PDF..."
|
||||||
|
- "Merge these PDFs..."
|
||||||
|
- "Extract text from this PDF..."
|
||||||
|
|
||||||
|
**Best for:** Final deliverables for external sharing, forms, archived documents.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### MPM Brand Voice — `mpm-brand-voice:brand-voice-enforcement` skill
|
||||||
|
**Invoke when:** User wants content that should reflect MPM's brand voice — emails, proposals, LinkedIn posts, website copy, sales content, client communications, or anything where "on-brand" matters.
|
||||||
|
|
||||||
|
**Natural trigger phrases:**
|
||||||
|
- "Use MPM's brand voice..."
|
||||||
|
- "Write this in our brand tone..."
|
||||||
|
- "Apply MPM's voice and style..."
|
||||||
|
- "This should sound like MPM..."
|
||||||
|
|
||||||
|
**When in doubt, include this for:** Any external-facing content, client communications, marketing materials, social posts.
|
||||||
|
|
||||||
|
**Do NOT include for:** Internal-only documents, data analysis, research summaries.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### Odoo (MPM ERP) — `odoo-mpm:odoo` skill
|
||||||
|
**Invoke when:** The prompt involves looking up MPM business data — contacts, clients, products, projects, tasks, sales orders, CRM leads, helpdesk tickets, inventory, or employee information.
|
||||||
|
|
||||||
|
**Natural trigger phrases:**
|
||||||
|
- "Look up [contact/client/product] in our system..."
|
||||||
|
- "Pull the current status of [project/ticket/lead]..."
|
||||||
|
- "Find [X] in Odoo..."
|
||||||
|
- "Check our CRM for..."
|
||||||
|
|
||||||
|
**Best for:** Any prompt that starts with gathering MPM data before creating something.
|
||||||
|
|
||||||
|
**For product specs specifically:** Use Odoo as a fallback when the Display Catalog skill is not available. MPM manufactures all its own displays — never direct Claude to search the web for MPM product information.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Multi-Skill Scenarios
|
||||||
|
|
||||||
|
Some prompts benefit from combining skills. Common combinations:
|
||||||
|
|
||||||
|
| User goal | Skills to invoke |
|
||||||
|
|---|---|
|
||||||
|
| Client proposal (Word, on-brand) | `docx` + `mpm-brand-voice:brand-voice-enforcement` |
|
||||||
|
| Sales pitch deck (on-brand) | `pptx` + `mpm-brand-voice:brand-voice-enforcement` |
|
||||||
|
| Quarterly report (Word, pull data) | `docx` + `odoo-mpm:odoo` |
|
||||||
|
| Client contact sheet (Excel, pull data) | `xlsx` + `odoo-mpm:odoo` |
|
||||||
|
| LinkedIn post about a win | `mpm-brand-voice:brand-voice-enforcement` |
|
||||||
|
|
||||||
|
When combining skills, include both trigger phrases naturally in the optimized prompt. For example:
|
||||||
|
> "Look up our Q1 closed deals in Odoo, then create a Word document summarizing the results for the MPM leadership team. Use a professional but direct tone."
|
||||||
|
|
||||||
|
This naturally triggers both `odoo-mpm:odoo` and `docx`.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Skills NOT to invoke proactively
|
||||||
|
|
||||||
|
These skills have their own specific triggers and should not be included in optimized prompts unless the user explicitly asks:
|
||||||
|
|
||||||
|
- `schedule` — Only if user mentions scheduling or recurring tasks
|
||||||
|
- `skill-creator` — Only if user is building or editing a skill
|
||||||
|
- Engineering skills (`engineering:*`) — Only for technical/software engineering tasks
|
||||||
|
- `mpm-brand-voice:guideline-generation` — Only if updating brand guidelines, not applying them
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## When No Skill Is Needed
|
||||||
|
|
||||||
|
Not every prompt needs a skill. Skip skill invocation when:
|
||||||
|
- The output is a simple conversational reply
|
||||||
|
- The user wants Claude to think, analyze, or explain something
|
||||||
|
- The output is short enough to live in the chat (under ~300 words)
|
||||||
|
- The user explicitly says they just want a quick answer
|
||||||
Reference in New Issue
Block a user