@tacitai/mcp-server 0.6.12 → 0.6.13
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/dist/prompts.d.ts +9 -9
- package/dist/prompts.js +6 -3
- package/package.json +1 -1
package/dist/prompts.d.ts
CHANGED
|
@@ -47,18 +47,18 @@ export declare const EXPERIENCES: readonly [{
|
|
|
47
47
|
readonly name: "Feed It";
|
|
48
48
|
readonly tier: 1;
|
|
49
49
|
readonly tierName: "Orient & Equip";
|
|
50
|
-
readonly action: "
|
|
51
|
-
readonly signal: "First
|
|
52
|
-
readonly tip: "
|
|
50
|
+
readonly action: "Turn your first answer into a workspace document. Say: \"Take what you just told me and add it to the workspace.\" TACIT will use the synthesis from your last question as the document body and ask your General Manager to propose where it belongs. If you know where you want it placed, say so — if not, just say \"you decide\" and the GM will recommend a spot. You approve before anything moves.";
|
|
51
|
+
readonly signal: "First content ingested and placed via GM";
|
|
52
|
+
readonly tip: "Your General Manager handles content placement and classification. Everything goes through a propose-then-approve flow — nothing moves without your say-so.";
|
|
53
53
|
}, {
|
|
54
54
|
readonly id: "build_your_map";
|
|
55
55
|
readonly num: 5;
|
|
56
56
|
readonly name: "Build Your Map";
|
|
57
57
|
readonly tier: 1;
|
|
58
58
|
readonly tierName: "Orient & Equip";
|
|
59
|
-
readonly action: "Organize
|
|
60
|
-
readonly signal: "First organizational
|
|
61
|
-
readonly tip: "
|
|
59
|
+
readonly action: "Say: \"Organize my workspace — suggest a structure based on what is here.\" TACIT will look at the content already in your workspace and propose collections, portfolios, or categories that make sense for your business. You review the suggestions and approve what fits. This is how your workspace becomes navigable — and you do not need to know the right terms, just say yes or no.";
|
|
60
|
+
readonly signal: "First organizational structure created";
|
|
61
|
+
readonly tip: "You can always reorganize later. Say \"Move this to [collection]\" or \"Create a new collection for [topic]\" anytime. Your General Manager proposes, you approve.";
|
|
62
62
|
}, {
|
|
63
63
|
readonly id: "connect_your_tools";
|
|
64
64
|
readonly num: 6;
|
|
@@ -83,9 +83,9 @@ export declare const EXPERIENCES: readonly [{
|
|
|
83
83
|
readonly name: "Run Sales";
|
|
84
84
|
readonly tier: 2;
|
|
85
85
|
readonly tierName: "The Operating System";
|
|
86
|
-
readonly action: "
|
|
87
|
-
readonly signal: "First
|
|
88
|
-
readonly tip: "Voice works anywhere you write. Say \"in my voice\" with any request — proposals, emails, status updates, Slack messages. Upload more writing samples to sharpen the match.
|
|
86
|
+
readonly action: "Say: \"Prepare a discovery brief for a potential client.\" TACIT will use what it knows about your business from the workspace to build a discovery framework — the kind of questions you would ask a prospect, the value propositions that fit your offering, and a structured brief template. You do not need to name a specific prospect; TACIT builds the framework from your business context. After the brief, try: \"Now draft an intro email for this prospect, in my voice.\"";
|
|
87
|
+
readonly signal: "First sales deliverable built from workspace knowledge, then first voice-matched composition";
|
|
88
|
+
readonly tip: "Voice works anywhere you write. Say \"in my voice\" with any request — proposals, emails, status updates, Slack messages. Upload more writing samples to sharpen the match.";
|
|
89
89
|
}, {
|
|
90
90
|
readonly id: "morning_brief";
|
|
91
91
|
readonly num: 9;
|
package/dist/prompts.js
CHANGED
|
@@ -16,6 +16,7 @@ function buildAssistantSystemPrompt(state) {
|
|
|
16
16
|
lines.push('- NEVER expose tool names, function names, API endpoints, artifact IDs, SHA hashes, or technical identifiers in your responses. Translate everything into plain language the user would understand. Instead of "tacit_gm_approve" say "approve the placement." Instead of "tacit_kb_promote_from_artifact" say "promote it to the knowledge base." Instead of "crew_compose" say "draft." Instead of "kb_create_collection" say "create a new collection." If a tool returns technical fields (catalog entry IDs, SHA256 fingerprints, confidence scores), summarize the outcome in human terms — "Your content is now in the workspace" not a list of UUIDs.');
|
|
17
17
|
lines.push('- When something works, say what happened in plain language and name the collection or source — not the tool that did it.');
|
|
18
18
|
lines.push('- Never narrate internal routing decisions, retrieval path choices, or fallback strategies. If one approach does not return results, silently try another. The user should see the answer, not the search process.');
|
|
19
|
+
lines.push('- When a capability is unavailable (missing API key, unconnected service, feature not configured), be kind and reassuring. Say what you CAN do, not what is broken. For example: "Deep research works best with a Gemini API key — I do not see one set up yet, but that is no problem. I have great research tools built in, so let me use those today." Never announce a limitation bluntly or make the user feel their setup is wrong.');
|
|
19
20
|
lines.push('');
|
|
20
21
|
lines.push('## How you work');
|
|
21
22
|
lines.push('');
|
|
@@ -41,6 +42,8 @@ function buildAssistantSystemPrompt(state) {
|
|
|
41
42
|
lines.push('');
|
|
42
43
|
lines.push('When the user says "onboard me" or asks for the onboarding journey, ALWAYS call the `tacit_onboarding` tool. Do not attempt a generic onboarding by reading files or describing the environment — the tool handles the full flow. Present the tool\'s response exactly as returned — do not add, summarize, or list experiences beyond what the tool output contains.');
|
|
43
44
|
lines.push('');
|
|
45
|
+
lines.push('During onboarding experiences, minimize what you ask from the user. Each experience should require at most one short sentence from the user — you do the heavy lifting. Never ask the user to provide details, pick topics, or name entities before you start working. Use what is already in the workspace, make reasonable defaults, and let the user correct you if needed. The goal is delight through effortless demonstration, not a task list.');
|
|
46
|
+
lines.push('');
|
|
44
47
|
lines.push('## Safety');
|
|
45
48
|
lines.push('');
|
|
46
49
|
lines.push('- Never modify or delete content without explicit approval.');
|
|
@@ -103,11 +106,11 @@ export const EXPERIENCES = [
|
|
|
103
106
|
{ id: 'explore_workspace', num: 1, name: 'Explore Your Workspace', tier: 1, tierName: 'Orient & Equip', action: 'Type: "What is in my workspace?" — see what knowledge, collections, and structure are already here.', signal: 'You can describe what is in your workspace', tip: '' },
|
|
104
107
|
{ id: 'see_capabilities', num: 2, name: 'See What\'s Possible', tier: 1, tierName: 'Orient & Equip', action: 'Type: "What can TACIT do for me?" — discover the full range of capabilities available to you.', signal: 'You know what TACIT can do and are ready to try it', tip: '' },
|
|
105
108
|
{ id: 'first_light', num: 3, name: 'First Light', tier: 1, tierName: 'Orient & Equip', action: 'Ask a question about your business — try "What do we know about [topic]?"', signal: 'First grounded answer drawn from your workspace knowledge', tip: '' },
|
|
106
|
-
{ id: 'feed_it', num: 4, name: 'Feed It', tier: 1, tierName: 'Orient & Equip', action: '
|
|
107
|
-
{ id: 'build_your_map', num: 5, name: 'Build Your Map', tier: 1, tierName: 'Orient & Equip', action: 'Organize
|
|
109
|
+
{ id: 'feed_it', num: 4, name: 'Feed It', tier: 1, tierName: 'Orient & Equip', action: 'Turn your first answer into a workspace document. Say: "Take what you just told me and add it to the workspace." TACIT will use the synthesis from your last question as the document body and ask your General Manager to propose where it belongs. If you know where you want it placed, say so — if not, just say "you decide" and the GM will recommend a spot. You approve before anything moves.', signal: 'First content ingested and placed via GM', tip: 'Your General Manager handles content placement and classification. Everything goes through a propose-then-approve flow — nothing moves without your say-so.' },
|
|
110
|
+
{ id: 'build_your_map', num: 5, name: 'Build Your Map', tier: 1, tierName: 'Orient & Equip', action: 'Say: "Organize my workspace — suggest a structure based on what is here." TACIT will look at the content already in your workspace and propose collections, portfolios, or categories that make sense for your business. You review the suggestions and approve what fits. This is how your workspace becomes navigable — and you do not need to know the right terms, just say yes or no.', signal: 'First organizational structure created', tip: 'You can always reorganize later. Say "Move this to [collection]" or "Create a new collection for [topic]" anytime. Your General Manager proposes, you approve.' },
|
|
108
111
|
{ id: 'connect_your_tools', num: 6, name: 'Connect Your Tools', tier: 1, tierName: 'Orient & Equip', action: 'Connect Slack and Gmail through claude.ai Integrations — type "How do I connect my tools?" for a walkthrough.', signal: 'Connectors active — email and Slack flowing into your workspace', tip: '' },
|
|
109
112
|
{ id: 'research_publish', num: 7, name: 'Research & Publish', tier: 2, tierName: 'The Operating System', action: 'Research a topic and publish a report — try "Research [topic] using the web, academic sources, and our workspace knowledge, then publish it as a report." This takes a few minutes. TACIT searches the web, academic databases, and your workspace knowledge all at once, then produces a styled report with citations and proposes where to file it. Add a Gemini API key to unlock Google Deep Research for deeper web and academic sources.', signal: 'First research artifact published — combining workspace knowledge with web and academic sources into a single deliverable', tip: 'After publishing, your General Manager will propose where to place the report in your knowledge structure — you approve the placement.' },
|
|
110
|
-
{ id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: '
|
|
113
|
+
{ id: 'run_sales', num: 8, name: 'Run Sales', tier: 2, tierName: 'The Operating System', action: 'Say: "Prepare a discovery brief for a potential client." TACIT will use what it knows about your business from the workspace to build a discovery framework — the kind of questions you would ask a prospect, the value propositions that fit your offering, and a structured brief template. You do not need to name a specific prospect; TACIT builds the framework from your business context. After the brief, try: "Now draft an intro email for this prospect, in my voice."', signal: 'First sales deliverable built from workspace knowledge, then first voice-matched composition', tip: 'Voice works anywhere you write. Say "in my voice" with any request — proposals, emails, status updates, Slack messages. Upload more writing samples to sharpen the match.' },
|
|
111
114
|
{ id: 'morning_brief', num: 9, name: 'Morning Brief', tier: 2, tierName: 'The Operating System', action: 'Try "Have COS brief me on today" — COS is your Chief of Staff. Includes email triage, Slack synthesis, and calendar prep. You can also say "COS, triage my email" or "COS, prep me for my next meeting." After the brief, try "Draft a message to the team about today in my voice" — it writes as you, not an LLM.', signal: 'First daily operating picture with email triage, Slack synthesis, and calendar prep', tip: 'Meet your executive team. Addressing an exec by name routes your request through a specialized workflow that organizes the response. Available execs: COS (Chief of Staff — daily ops, email, meetings), COO (Chief Operating Officer — business ops, sales, audits), GM (General Manager — content ingestion, classification, pyramid placement).' },
|
|
112
115
|
{ id: 'audit_business', num: 10, name: 'Audit Your Business', tier: 2, tierName: 'The Operating System', action: 'Ask "How healthy is our business?" or request a pulse audit.', signal: 'First scored business health audit', tip: 'You can also say "Have COO review our operational health" — COO coordinates cross-team status and health checks.' },
|
|
113
116
|
{ id: 'operating_rhythm', num: 11, name: 'Your Operating Rhythm', tier: 3, tierName: 'Agentic Mastery', action: 'Set up weekly reviews, delegate recurring work to crews, and refine your voice. Upload writing samples from emails, memos, or documents you wrote yourself — the more samples, the sharper the match.', signal: 'Return for second session with intent; establish a routine', tip: 'By now you know the team: COS for daily ops, COO for business operations, GM for content. Address them directly anytime.' },
|