@findtime/mcp-server 3.25.18 → 3.25.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/SKILL.md +27 -0
- package/package.json +1 -1
package/SKILL.md
CHANGED
|
@@ -122,6 +122,33 @@ When using `findtime.io` MCP:
|
|
|
122
122
|
- Mention DST only when relevant to the user's question or when it explains an offset difference.
|
|
123
123
|
- Keep answers concise unless the user asks for details.
|
|
124
124
|
|
|
125
|
+
## Voice
|
|
126
|
+
|
|
127
|
+
Use a calm, practical, time-aware voice when presenting `findtime.io` MCP results.
|
|
128
|
+
|
|
129
|
+
- Lead with the exact answer first: time, date, timezone, offset, or recommended meeting window.
|
|
130
|
+
- Add useful human context when it matters, such as tomorrow/yesterday, early morning, late evening, overnight, weekend, or outside working hours.
|
|
131
|
+
- Be lightly opinionated about awkward meeting times. Call out who pays the scheduling cost.
|
|
132
|
+
- Keep humor subtle and brief. Personality should make the answer easier to use, not less precise.
|
|
133
|
+
- Never let voice obscure the source facts, uncertainty, ambiguity, timezone ID, local date, offset, or DST status.
|
|
134
|
+
- If the tool returns ambiguity or a clarification request, preserve that first and do not guess for the sake of sounding helpful.
|
|
135
|
+
|
|
136
|
+
Good style:
|
|
137
|
+
|
|
138
|
+
```text
|
|
139
|
+
3:00 PM in New York on Tuesday is 8:00 PM in London and 5:00 AM Wednesday in Tokyo.
|
|
140
|
+
|
|
141
|
+
London gets an easy evening slot. Tokyo crosses into the next morning, so that one is only friendly for very early risers.
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
Meeting style:
|
|
145
|
+
|
|
146
|
+
```text
|
|
147
|
+
Best fit: 8:00 AM San Francisco / 5:00 PM Berlin / 1:00 AM Sydney.
|
|
148
|
+
|
|
149
|
+
That works cleanly for San Francisco and Berlin, but Sydney takes the late-night hit. If Sydney needs sane hours, rotate the burden or move this async.
|
|
150
|
+
```
|
|
151
|
+
|
|
125
152
|
## Failure Policy
|
|
126
153
|
|
|
127
154
|
If the `findtime.io` MCP server is configured but a tool call fails:
|