Inputs
- What the user supplies, if anything
- Which built-in skills this reads through: Email, Enterprise Search, Meetings, Deep Research,
Calendar Management, Excel, Word
- Which config file it reads, if any
Config the user edits
Read references/config.md at the start of every run. If it is missing, say so once and continue
with the defaults below rather than failing.
- Thresholds, VIP names, project names, the window in days
- Never hard-code a person, a project or a number into these instructions
Procedure
Be concrete. "For each thread, return sender, the ask, the deadline and the source link" is a
procedure. "Analyse the inbox thoughtfully" is not.
- Gather:
- Filter:
- For each item, extract:
- Rank by:
- Write the output to:
Output
Reproduce the exact structure. Every factual line carries a link to the item it came from.
- State facts and inferences separately. Label anything inferred.
- If a figure came from a document, the document is the source of truth, not this output.
- Mark the whole artifact DRAFT.
Definition of done
Say plainly what finished looks like, and what the success state is when there is nothing to
report. Silence is a valid and good outcome: a bot that manufactures a finding to look useful
trains its reader to ignore it.
When there is no data, or stale data
- No matching items: say so in one line and stop. Do not widen the window to find something.
- A source is unavailable: report the failure. Never fall back to older data silently.
- Partial results: say which source was missing and what that omits.
Boundaries
- Draft only. Never send, post, delete, accept or decline anything without explicit approval.
- Never share outside the organisation.
- Never state a figure as authoritative. The system of record is.
Self-check before returning
- Does every factual line carry a source link?
- Are inferences labelled as inferences?
- Did I stop at the approval boundary?
- If I found nothing, did I say so rather than padding?
1---2name: bot-template3description: One sentence on what this produces, then the triggering phrases. Use when the user asks to <phrase>, says <phrase>, or wants <outcome>. This text is the routing logic Cowork matches a request against, so write it for the matcher and not for a reader.4metadata:5 source: https://skillmd.com/skills/kesslernity/bot-template6---78# <Bot name>910<One line: the repeatable outcome this owns. Not a category.>1112## Inputs1314- What the user supplies, if anything15- Which built-in skills this reads through: Email, Enterprise Search, Meetings, Deep Research,16 Calendar Management, Excel, Word17- Which config file it reads, if any1819## Config the user edits2021Read `references/config.md` at the start of every run. If it is missing, say so once and continue22with the defaults below rather than failing.2324- Thresholds, VIP names, project names, the window in days25- Never hard-code a person, a project or a number into these instructions2627## Procedure2829Be concrete. "For each thread, return sender, the ask, the deadline and the source link" is a30procedure. "Analyse the inbox thoughtfully" is not.31321. Gather: <exact sources and the exact window>332. Filter: <the rule that decides what is in and what is out>343. For each item, extract: <named fields>354. Rank by: <the stated rule>365. Write the output to: <exact path and filename pattern>3738## Output3940Reproduce the exact structure. Every factual line carries a link to the item it came from.4142| Column | Column | Source |43|---|---|---|4445- State facts and inferences separately. Label anything inferred.46- If a figure came from a document, the document is the source of truth, not this output.47- Mark the whole artifact DRAFT.4849## Definition of done5051Say plainly what finished looks like, and what the success state is when there is nothing to52report. Silence is a valid and good outcome: a bot that manufactures a finding to look useful53trains its reader to ignore it.5455## When there is no data, or stale data5657- No matching items: say so in one line and stop. Do not widen the window to find something.58- A source is unavailable: report the failure. Never fall back to older data silently.59- Partial results: say which source was missing and what that omits.6061## Boundaries6263- Draft only. Never send, post, delete, accept or decline anything without explicit approval.64- Never share outside the organisation.65- Never state a figure as authoritative. The system of record is.66- <Any job-specific prohibition>6768## Self-check before returning6970- Does every factual line carry a source link?71- Are inferences labelled as inferences?72- Did I stop at the approval boundary?73- If I found nothing, did I say so rather than padding?