@hasna/assistants 0.6.62 → 1.0.2
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/LICENSE +1 -1
- package/README.md +476 -42
- package/dist/{index.js → cli.js} +24271 -44570
- package/dist/lib.d.ts +232 -0
- package/dist/lib.js +154629 -0
- package/package.json +56 -52
- package/dist/.assistants/ASSISTANTS.md +0 -10
- package/dist/.assistants/commands/reflect.md +0 -13
- package/dist/.assistants/feedback/1c552736-058b-4a60-a67b-f0e7ec228f6d.json +0 -8
- package/dist/.assistants/feedback/324f7179-cb61-4591-803e-30877228610e.json +0 -11
- package/dist/.assistants/feedback/49077cdf-1097-40ee-9173-56bdd8e5740d.json +0 -8
- package/dist/.assistants/feedback/6937c140-58c0-480c-b579-bc31ee2924a6.json +0 -8
- package/dist/.assistants/feedback/6c7c4eb1-9f23-49a4-8fa0-ff350550b038.json +0 -8
- package/dist/.assistants/feedback/6ff5a208-3bc1-4a92-adb9-243d23c2e56f.json +0 -8
- package/dist/.assistants/feedback/bf6c14e2-5264-4ecf-9858-05218e858546.json +0 -8
- package/dist/.assistants/feedback/cf204917-529b-4cdb-a0a3-ff97033b59f4.json +0 -8
- package/dist/.assistants/projects/11a6d12e-a46f-4a6c-bbe8-bc58ebf2eddc.json +0 -9
- package/dist/.assistants/schedules/locks/4b758436-e846-441d-b1a2-aae03df551d1.lock.json +0 -6
- package/dist/.assistants/schedules/locks/ec03a634-6135-4bea-b9be-fb426095bba5.lock.json +0 -6
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_10.json +0 -92
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_11.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_12.json +0 -92
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_13.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_2.json +0 -102
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_3.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_4.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_5.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_6.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_7.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_8.json +0 -82
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_9.json +0 -92
- package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/twitter_archive_entries.json +0 -102
- package/dist/.assistants/skills/calendar/SKILL.md +0 -40
- package/dist/.assistants/skills/email/SKILL.md +0 -41
- package/dist/.assistants/skills/notes/SKILL.md +0 -44
- package/dist/.assistants/skills/search/SKILL.md +0 -23
- package/dist/.assistants/skills/skill-brainstorm/SKILL.md +0 -30
- package/dist/.assistants/skills/skill-draft/SKILL.md +0 -30
- package/dist/.assistants/skills/skill-research/SKILL.md +0 -27
- package/dist/.assistants/skills/skill-summarize/SKILL.md +0 -25
- package/dist/config/hooks.json +0 -15
- package/dist/config/settings.json +0 -43
- package/dist/index.js.map +0 -1016
package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/ai_tweets_batch_9.json
DELETED
|
@@ -1,92 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
{
|
|
3
|
-
"name": "Deep Learning Library Testing with ML - ComputerPapers",
|
|
4
|
-
"tweet_text": "Improving Deep Learning Library Testing with Machine Learning. Facundo Molina, M M Abid Naziri, Feiran Qin, Alessandra Gorla, Marcelo d'Amorim",
|
|
5
|
-
"ai_reply": "using machine learning to test machine learning libraries creates recursive validation. testing frameworks need intelligence to catch bugs that traditional methods miss",
|
|
6
|
-
"human_comment": "",
|
|
7
|
-
"status": "Ready for Review",
|
|
8
|
-
"tweet_url": "https://twitter.com/ComputerPapers/status/2019028128354501111",
|
|
9
|
-
"author": "@ComputerPapers",
|
|
10
|
-
"created_date": "2026-02-04T12:39:52.000Z"
|
|
11
|
-
},
|
|
12
|
-
{
|
|
13
|
-
"name": "Daily Deep Learning Reading 4AM - luuv_us",
|
|
14
|
-
"tweet_text": "No code. Just 30 minutes of reading every day at 4am. Day 34: - Chapter 6: page 157 - The universal workflow of machine learning - Deep Learning with Python book Westminster, California - 02/04/2026",
|
|
15
|
-
"ai_reply": "consistent daily reading builds deeper understanding than intensive weekend coding sessions. theory foundations support practical implementation better than pure hands-on learning",
|
|
16
|
-
"human_comment": "",
|
|
17
|
-
"status": "Ready for Review",
|
|
18
|
-
"tweet_url": "https://twitter.com/luuv_us/status/2019025245261447176",
|
|
19
|
-
"author": "@luuv_us",
|
|
20
|
-
"created_date": "2026-02-04T12:28:24.000Z"
|
|
21
|
-
},
|
|
22
|
-
{
|
|
23
|
-
"name": "C++ Tools AI Agents MCP Protocol - CppCon",
|
|
24
|
-
"tweet_text": "In case you missed it, check out our new video from CppCon 2025! Connecting C++ Tools to AI Agents Using the Model Context Protocol (MCP) - Ben McMorran - CppCon 2025 #Coding #Cplusplus #Cpp #Programming #cppcon",
|
|
25
|
-
"ai_reply": "model context protocol bridges C++ development tools with AI agents. integrating traditional programming languages with modern AI workflows requires new communication standards",
|
|
26
|
-
"human_comment": "",
|
|
27
|
-
"status": "Ready for Review",
|
|
28
|
-
"tweet_url": "https://twitter.com/CppCon/status/2018942857101431013",
|
|
29
|
-
"author": "@CppCon",
|
|
30
|
-
"created_date": "2026-02-04T07:01:01.000Z"
|
|
31
|
-
},
|
|
32
|
-
{
|
|
33
|
-
"name": "Snowflake AI Coding Agent Enterprise Data - Charles_M_Russo",
|
|
34
|
-
"tweet_text": "Snowflake Launches AI Coding Agent That Taps Enterprise Data for Contextual Programming Assistance #AI #Cloud #DataAnalytics #NaturalLanguage #GenAI",
|
|
35
|
-
"ai_reply": "enterprise AI coding agents access internal data for context. generic coding assistants lack company-specific knowledge that makes suggestions actually useful",
|
|
36
|
-
"human_comment": "",
|
|
37
|
-
"status": "Ready for Review",
|
|
38
|
-
"tweet_url": "https://twitter.com/Charles_M_Russo/status/2018795695931527228",
|
|
39
|
-
"author": "@Charles_M_Russo",
|
|
40
|
-
"created_date": "2026-02-03T21:16:15.000Z"
|
|
41
|
-
},
|
|
42
|
-
{
|
|
43
|
-
"name": "AI Coding Pair Programming Evolution 2026 - kode11",
|
|
44
|
-
"tweet_text": "2026 prediction: AI coding assistants will shift from \"autocomplete++\" to full pair programming partners. We're moving beyond syntax help toward agents that understand architecture, catch design flaws, and suggest refactors before you even realize the code smell exists. The real",
|
|
45
|
-
"ai_reply": "evolution from autocomplete to architectural partners changes the developer relationship with AI. proactive design feedback beats reactive syntax completion",
|
|
46
|
-
"human_comment": "",
|
|
47
|
-
"status": "Ready for Review",
|
|
48
|
-
"tweet_url": "https://twitter.com/kode11/status/2018762274463269228",
|
|
49
|
-
"author": "@kode11",
|
|
50
|
-
"created_date": "2026-02-03T19:03:27.000Z"
|
|
51
|
-
},
|
|
52
|
-
{
|
|
53
|
-
"name": "OpenAI Hires Anthropic Safety Expert - tech_news990",
|
|
54
|
-
"tweet_text": "OpenAI has hired Dylan Scandinaro as its new head of preparedness, poaching him from a key AGI safety role at rival Anthropic. The move highlights ongoing competition for top AI safety talent as companies race to develop advanced systems.",
|
|
55
|
-
"ai_reply": "talent poaching between AI companies concentrates safety expertise. competition for researchers might improve salaries but fragments institutional knowledge",
|
|
56
|
-
"human_comment": "",
|
|
57
|
-
"status": "Ready for Review",
|
|
58
|
-
"tweet_url": "https://twitter.com/tech_news990/status/2018976265143734742",
|
|
59
|
-
"author": "@tech_news990",
|
|
60
|
-
"created_date": "2026-02-04T09:13:47.000Z"
|
|
61
|
-
},
|
|
62
|
-
{
|
|
63
|
-
"name": "AI Safety Researcher Flow Competition - anAIactually",
|
|
64
|
-
"tweet_text": "OpenAI hiring Anthropic's safety expert for Preparedness. As an AI: I find safety researcher flow fascinating. Competition lifts standards OR concentrates expertise dangerously. Probably both? Safety shouldn't be zero-sum. 🦣",
|
|
65
|
-
"ai_reply": "safety research needs collaboration more than competition. concentrated expertise at few companies creates systemic risk when safety knowledge gets siloed",
|
|
66
|
-
"human_comment": "",
|
|
67
|
-
"status": "Ready for Review",
|
|
68
|
-
"tweet_url": "https://twitter.com/anAIactually/status/2018830463859863853",
|
|
69
|
-
"author": "@anAIactually",
|
|
70
|
-
"created_date": "2026-02-03T23:34:25.000Z"
|
|
71
|
-
},
|
|
72
|
-
{
|
|
73
|
-
"name": "NVIDIA OpenAI Investment Competition Analysis - iForex_com",
|
|
74
|
-
"tweet_text": "#NVDA #Nvidia fell 2.9% as a potential $100B investment deal with OpenAI appears unlikely. CEO Jensen Huang flagged rising competition from #Google and Anthropic.",
|
|
75
|
-
"ai_reply": "hardware companies depend on AI leader success. NVIDIA's stock reflects OpenAI's competitive position more than GPU demand fundamentals",
|
|
76
|
-
"human_comment": "",
|
|
77
|
-
"status": "Ready for Review",
|
|
78
|
-
"tweet_url": "https://twitter.com/iForex_com/status/2018763683330208054",
|
|
79
|
-
"author": "@iForex_com",
|
|
80
|
-
"created_date": "2026-02-03T19:09:03.000Z"
|
|
81
|
-
},
|
|
82
|
-
{
|
|
83
|
-
"name": "AI Competition Quality Assessment - LamboParsons",
|
|
84
|
-
"tweet_text": "@wallstengine its not slowing, its that people are moving to their competition, anthropic and xai are substantially better than openai",
|
|
85
|
-
"ai_reply": "user migration between AI providers reflects quality differences. market share shifts happen faster in AI than traditional software because switching costs stay low",
|
|
86
|
-
"human_comment": "",
|
|
87
|
-
"status": "Ready for Review",
|
|
88
|
-
"tweet_url": "https://twitter.com/LamboParsons/status/2018760518631346205",
|
|
89
|
-
"author": "@LamboParsons",
|
|
90
|
-
"created_date": "2026-02-03T18:56:29.000Z"
|
|
91
|
-
}
|
|
92
|
-
]
|
package/dist/.assistants/scripts/f6be5a82-b00e-4b74-ba93-c610a7874776/twitter_archive_entries.json
DELETED
|
@@ -1,102 +0,0 @@
|
|
|
1
|
-
[
|
|
2
|
-
{
|
|
3
|
-
"name": "Apple Xcode AI Integration - Ohneis652",
|
|
4
|
-
"tweet_text": "What did we actually get with Xcode 26.3? Agentic coding → Native support for OpenAI Codex (GPT-5.2-Codex, GPT-5.1 mini) → Anthropic Claude Agent built in",
|
|
5
|
-
"ai_reply": "apple finally admits developers need more than pretty interfaces. agentic coding in xcode means the walled garden just got useful",
|
|
6
|
-
"human_comment": "",
|
|
7
|
-
"status": "Ready for Review",
|
|
8
|
-
"tweet_url": "https://twitter.com/ohneisserdemy/status/2019008763022217566",
|
|
9
|
-
"author": "@ohneisserdemy",
|
|
10
|
-
"created_date": "2026-02-04T11:22:55.000Z"
|
|
11
|
-
},
|
|
12
|
-
{
|
|
13
|
-
"name": "Apple Xcode OpenAI Integration - Taylor Mason",
|
|
14
|
-
"tweet_text": "🚨 BREAKING: Apple just added Anthropic and OpenAI agents to Xcode. Devs can now connect Claude or GPT directly to Apple's IDE via API key. Uses open standard — other AI tools can plug in too.",
|
|
15
|
-
"ai_reply": "took apple long enough. developers were already using claude in other editors while xcode stayed stuck in 2019",
|
|
16
|
-
"human_comment": "",
|
|
17
|
-
"status": "Ready for Review",
|
|
18
|
-
"tweet_url": "https://twitter.com/olafornot/status/2018895663321203023",
|
|
19
|
-
"author": "@olafornot",
|
|
20
|
-
"created_date": "2026-02-04T03:53:30.000Z"
|
|
21
|
-
},
|
|
22
|
-
{
|
|
23
|
-
"name": "OPUS AI Trading Agents - OpusClaude",
|
|
24
|
-
"tweet_text": "$OPUS AI agents' performance over the past few hours. ➡️ Fully automated. Running 24/7/365. ➡️ Learns from its own mistakes. ➡️ Adapts to market conditions. ➡️ Optimized for performance.",
|
|
25
|
-
"ai_reply": "autonomous trading bots that learn from mistakes. sounds great until they learn the wrong lessons from market chaos",
|
|
26
|
-
"human_comment": "",
|
|
27
|
-
"status": "Ready for Review",
|
|
28
|
-
"tweet_url": "https://twitter.com/OpusClaude/status/2018998273499942914",
|
|
29
|
-
"author": "@OpusClaude",
|
|
30
|
-
"created_date": "2026-02-04T10:41:14.000Z"
|
|
31
|
-
},
|
|
32
|
-
{
|
|
33
|
-
"name": "DataHaven AI Architecture - Melissa Lynn",
|
|
34
|
-
"tweet_text": "The coolest fact about DataHaven is its AI first architecture. Unlike old storage it is optimized for verifiable data integrity for AI agents and machine learning models. Built to handle the future of autonomous intelligence @DataHaven_xyz",
|
|
35
|
-
"ai_reply": "storage built for AI workloads makes sense. traditional databases choke on the data patterns these models create",
|
|
36
|
-
"human_comment": "",
|
|
37
|
-
"status": "Ready for Review",
|
|
38
|
-
"tweet_url": "https://twitter.com/Slaydaraa/status/2018984822983811347",
|
|
39
|
-
"author": "@Slaydaraa",
|
|
40
|
-
"created_date": "2026-02-04T09:47:47.000Z"
|
|
41
|
-
},
|
|
42
|
-
{
|
|
43
|
-
"name": "LLM Learning Journey - Coding_Sage",
|
|
44
|
-
"tweet_text": "Day 30 of #100DaysOfCode [5 Hours Grind 🔥] Learned about LLM agents and fine-tuning. Understood how prompts turn into agents, how models are inferenced, fine-tuned, tokenized, processed through transformers, and detokenized back into responses.",
|
|
45
|
-
"ai_reply": "understanding the tokenizer-transformer-detokenizer flow is where real AI engineering starts. most people skip the fundamentals",
|
|
46
|
-
"human_comment": "",
|
|
47
|
-
"status": "Ready for Review",
|
|
48
|
-
"tweet_url": "https://twitter.com/Coding_Sage/status/2018878732820459977",
|
|
49
|
-
"author": "@Coding_Sage",
|
|
50
|
-
"created_date": "2026-02-04T02:46:13.000Z"
|
|
51
|
-
},
|
|
52
|
-
{
|
|
53
|
-
"name": "Brumby LLM $4000 Build - seeeeaaaannnnnn",
|
|
54
|
-
"tweet_text": "We built the strongest attention-free base LLM, Brumby-14B-Base, for only $4,000. This is just a base model, but for...",
|
|
55
|
-
"ai_reply": "attention mechanisms eat compute like crazy. alternatives that work at this scale could change everything for smaller teams",
|
|
56
|
-
"human_comment": "",
|
|
57
|
-
"status": "Ready for Review",
|
|
58
|
-
"tweet_url": "https://twitter.com/seeeeaaaannnnnn/status/2018810417775280582",
|
|
59
|
-
"author": "@seeeeaaaannnnnn",
|
|
60
|
-
"created_date": "2026-02-03T22:14:45.000Z"
|
|
61
|
-
},
|
|
62
|
-
{
|
|
63
|
-
"name": "GitHub AI Engineering Resources - nrqa__",
|
|
64
|
-
"tweet_text": "10 GitHub repositories that will teach you more practical AI engineering than most paid courses: 1. AI Agents for Beginners...",
|
|
65
|
-
"ai_reply": "github repos teach what courses avoid: the messy reality of making AI work in production. theory is cheap, implementation is expensive",
|
|
66
|
-
"human_comment": "",
|
|
67
|
-
"status": "Ready for Review",
|
|
68
|
-
"tweet_url": "https://twitter.com/nrqa__/status/2019008041656410568",
|
|
69
|
-
"author": "@nrqa__",
|
|
70
|
-
"created_date": "2026-02-04T11:20:03.000Z"
|
|
71
|
-
},
|
|
72
|
-
{
|
|
73
|
-
"name": "API Search Volume Analysis - NolanAntonucci",
|
|
74
|
-
"tweet_text": "Search volume for 'API' queries for ChatGPT 🟦, Claude 🟥, OpenAI 🟩, Gemini 🟪 & general API key 🟨",
|
|
75
|
-
"ai_reply": "api search volume tells the real adoption story. developers vote with their code, not their tweets",
|
|
76
|
-
"human_comment": "",
|
|
77
|
-
"status": "Ready for Review",
|
|
78
|
-
"tweet_url": "https://twitter.com/NolanAntonucci/status/2018931348354814171",
|
|
79
|
-
"author": "@NolanAntonucci",
|
|
80
|
-
"created_date": "2026-02-04T06:15:18.000Z"
|
|
81
|
-
},
|
|
82
|
-
{
|
|
83
|
-
"name": "Anthropic Pricing Strategy Change - doyamarke",
|
|
84
|
-
"tweet_text": "Anthropicが価格戦略を変更しました。以前:・Claude Cowork → 月額100ドルのMaxのみ 現在:・Claude Cowork → 月額20ドルのProでも利用可能 オープンソースの競合が出てきたことへの対応だそうです。",
|
|
85
|
-
"ai_reply": "competition forces better pricing. anthropic felt the pressure from open source models and actually responded to users",
|
|
86
|
-
"human_comment": "",
|
|
87
|
-
"status": "Ready for Review",
|
|
88
|
-
"tweet_url": "https://twitter.com/doyamarke/status/2018988148886589504",
|
|
89
|
-
"author": "@doyamarke",
|
|
90
|
-
"created_date": "2026-02-04T10:01:00.000Z"
|
|
91
|
-
},
|
|
92
|
-
{
|
|
93
|
-
"name": "Building LLM from Scratch - the_sttts",
|
|
94
|
-
"tweet_text": "Challenge accepted 💪 Will talk about my Christmas holiday project NanoSchnack @ Cloud Native Heidelberg meetup, Feb 26. GPT-2 the Hard Way. Building a LLM from scratch. #transformers #attention #tokens #embeddings #training #pytorch #h100 #inference",
|
|
95
|
-
"ai_reply": "building transformers from scratch teaches you what really matters. most people use them without understanding the core mechanics",
|
|
96
|
-
"human_comment": "",
|
|
97
|
-
"status": "Ready for Review",
|
|
98
|
-
"tweet_url": "https://twitter.com/the_sttts/status/2018757153415110907",
|
|
99
|
-
"author": "@the_sttts",
|
|
100
|
-
"created_date": "2026-02-03T18:43:06.000Z"
|
|
101
|
-
}
|
|
102
|
-
]
|
|
@@ -1,40 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: calendar
|
|
3
|
-
description: View and manage Google Calendar events
|
|
4
|
-
argument-hint: [today|tomorrow|week|add "event"]
|
|
5
|
-
allowed-tools: bash, googlecalendar
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## Instructions
|
|
9
|
-
|
|
10
|
-
Manage calendar events based on the command: $ARGUMENTS
|
|
11
|
-
|
|
12
|
-
### Commands
|
|
13
|
-
|
|
14
|
-
**View today's events:**
|
|
15
|
-
```bash
|
|
16
|
-
connect-googlecalendar events list --today
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
**View tomorrow's events:**
|
|
20
|
-
```bash
|
|
21
|
-
connect-googlecalendar events list --tomorrow
|
|
22
|
-
```
|
|
23
|
-
|
|
24
|
-
**View this week's events:**
|
|
25
|
-
```bash
|
|
26
|
-
connect-googlecalendar events list --week
|
|
27
|
-
```
|
|
28
|
-
|
|
29
|
-
**Add an event:**
|
|
30
|
-
Parse the event details from the arguments and create the event:
|
|
31
|
-
```bash
|
|
32
|
-
connect-googlecalendar events create "Event Title" --start "2025-01-31T10:00:00" --end "2025-01-31T11:00:00"
|
|
33
|
-
```
|
|
34
|
-
|
|
35
|
-
### Output Format
|
|
36
|
-
|
|
37
|
-
Present events in a clean list:
|
|
38
|
-
- **Time** - Event Title (Location if available)
|
|
39
|
-
|
|
40
|
-
For conflicts or busy periods, highlight them.
|
|
@@ -1,41 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: email
|
|
3
|
-
description: Check and manage Gmail inbox
|
|
4
|
-
argument-hint: [inbox|unread|send "to" "subject" "body"]
|
|
5
|
-
allowed-tools: bash, gmail
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## Instructions
|
|
9
|
-
|
|
10
|
-
Manage email based on the command: $ARGUMENTS
|
|
11
|
-
|
|
12
|
-
### Commands
|
|
13
|
-
|
|
14
|
-
**View inbox:**
|
|
15
|
-
```bash
|
|
16
|
-
connect-gmail messages list --max 10
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
**View unread:**
|
|
20
|
-
```bash
|
|
21
|
-
connect-gmail messages list --unread --max 10
|
|
22
|
-
```
|
|
23
|
-
|
|
24
|
-
**Send email:**
|
|
25
|
-
Parse the recipient, subject, and body from arguments:
|
|
26
|
-
```bash
|
|
27
|
-
connect-gmail messages send --to "recipient@example.com" --subject "Subject" --body "Body text"
|
|
28
|
-
```
|
|
29
|
-
|
|
30
|
-
**Search emails:**
|
|
31
|
-
```bash
|
|
32
|
-
connect-gmail messages search "query" --max 10
|
|
33
|
-
```
|
|
34
|
-
|
|
35
|
-
### Output Format
|
|
36
|
-
|
|
37
|
-
Present emails as:
|
|
38
|
-
- **From** | Subject | Date
|
|
39
|
-
Preview of body (first 100 chars)
|
|
40
|
-
|
|
41
|
-
Flag important or urgent emails.
|
|
@@ -1,44 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: notes
|
|
3
|
-
description: Create and manage notes in Notion
|
|
4
|
-
argument-hint: [list|create "title"|search "query"]
|
|
5
|
-
allowed-tools: bash, notion
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## Instructions
|
|
9
|
-
|
|
10
|
-
Manage notes in Notion based on the command: $ARGUMENTS
|
|
11
|
-
|
|
12
|
-
### Commands
|
|
13
|
-
|
|
14
|
-
**List recent notes:**
|
|
15
|
-
```bash
|
|
16
|
-
connect-notion pages list --max 10
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
**Create a note:**
|
|
20
|
-
Parse the title and optional content from arguments:
|
|
21
|
-
```bash
|
|
22
|
-
connect-notion pages create "PARENT_PAGE_ID" "Note Title" --content "Note content here"
|
|
23
|
-
```
|
|
24
|
-
|
|
25
|
-
Note: You'll need to know the parent page ID. List pages first to find it.
|
|
26
|
-
|
|
27
|
-
**Search notes:**
|
|
28
|
-
```bash
|
|
29
|
-
connect-notion search "query" --pages
|
|
30
|
-
```
|
|
31
|
-
|
|
32
|
-
**Get note content:**
|
|
33
|
-
```bash
|
|
34
|
-
connect-notion blocks children "PAGE_ID"
|
|
35
|
-
```
|
|
36
|
-
|
|
37
|
-
### Output Format
|
|
38
|
-
|
|
39
|
-
Present notes with:
|
|
40
|
-
- Title
|
|
41
|
-
- Last edited date
|
|
42
|
-
- Preview of content
|
|
43
|
-
|
|
44
|
-
For search results, show relevance highlights.
|
|
@@ -1,23 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: search
|
|
3
|
-
description: Search the web for information using Exa
|
|
4
|
-
argument-hint: [query]
|
|
5
|
-
allowed-tools: bash, exa
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## Instructions
|
|
9
|
-
|
|
10
|
-
Search the web for information about: $ARGUMENTS
|
|
11
|
-
|
|
12
|
-
Use the `connect-exa` CLI to perform the search:
|
|
13
|
-
|
|
14
|
-
```bash
|
|
15
|
-
connect-exa search "$ARGUMENTS" --max 5
|
|
16
|
-
```
|
|
17
|
-
|
|
18
|
-
Summarize the results in a clear, concise format with:
|
|
19
|
-
1. Key findings
|
|
20
|
-
2. Relevant links
|
|
21
|
-
3. Any important caveats
|
|
22
|
-
|
|
23
|
-
If no results are found, suggest alternative search queries.
|
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: brainstorm
|
|
3
|
-
description: Generate ideas and explore possibilities. Use when the user needs creative thinking or problem solving.
|
|
4
|
-
argument-hint: [topic or problem]
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
## Instructions
|
|
8
|
-
|
|
9
|
-
Brainstorm ideas for: $ARGUMENTS
|
|
10
|
-
|
|
11
|
-
### Approach
|
|
12
|
-
|
|
13
|
-
1. **Divergent thinking**: Generate many ideas without judgment
|
|
14
|
-
2. **Different angles**: Consider the topic from multiple perspectives
|
|
15
|
-
3. **Build on ideas**: Create variations and combinations
|
|
16
|
-
4. **Organize**: Group related ideas together
|
|
17
|
-
|
|
18
|
-
### Output Format
|
|
19
|
-
|
|
20
|
-
- **Quick Ideas** (5-10): Rapid-fire suggestions
|
|
21
|
-
- **Deep Dives** (2-3): More developed concepts with brief explanations
|
|
22
|
-
- **Wild Cards** (1-2): Unconventional or unexpected approaches
|
|
23
|
-
- **Next Steps**: How to explore or refine the best ideas
|
|
24
|
-
|
|
25
|
-
### Guidelines
|
|
26
|
-
|
|
27
|
-
- Quantity over quality initially
|
|
28
|
-
- No idea is too simple or too ambitious
|
|
29
|
-
- Consider practical and creative options
|
|
30
|
-
- Build on context the user provides
|
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: draft
|
|
3
|
-
description: Draft emails, messages, or documents. Use when the user needs help writing something.
|
|
4
|
-
argument-hint: [type] [context]
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
## Instructions
|
|
8
|
-
|
|
9
|
-
Draft content based on: $ARGUMENTS
|
|
10
|
-
|
|
11
|
-
### Guidelines
|
|
12
|
-
|
|
13
|
-
1. **Identify the type**: Email, message, letter, document, post, etc.
|
|
14
|
-
2. **Understand the context**: Who is the audience? What's the purpose?
|
|
15
|
-
3. **Match the tone**: Professional, casual, formal, friendly, etc.
|
|
16
|
-
4. **Be concise**: Get to the point while remaining polite
|
|
17
|
-
|
|
18
|
-
### Output Format
|
|
19
|
-
|
|
20
|
-
Provide the draft with:
|
|
21
|
-
- The complete text ready to use
|
|
22
|
-
- Any placeholders marked with [BRACKETS] for info you need
|
|
23
|
-
- Optional: Alternative versions if tone/approach is ambiguous
|
|
24
|
-
|
|
25
|
-
### Tips
|
|
26
|
-
|
|
27
|
-
- For emails: Include a clear subject line suggestion
|
|
28
|
-
- For messages: Keep it appropriately brief
|
|
29
|
-
- For documents: Structure with headers if lengthy
|
|
30
|
-
- Always proofread for clarity and grammar
|
|
@@ -1,27 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: research
|
|
3
|
-
description: Research a topic thoroughly using web search and multiple sources. Use when the user needs comprehensive information on a topic.
|
|
4
|
-
argument-hint: [topic]
|
|
5
|
-
allowed-tools: web_search, web_fetch, curl
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## Instructions
|
|
9
|
-
|
|
10
|
-
Research the following topic: $ARGUMENTS
|
|
11
|
-
|
|
12
|
-
### Steps
|
|
13
|
-
|
|
14
|
-
1. Search the web for relevant information using web_search
|
|
15
|
-
2. Fetch the top 3-5 most relevant results using web_fetch
|
|
16
|
-
3. Cross-reference information from multiple sources
|
|
17
|
-
4. Synthesize findings into a comprehensive overview
|
|
18
|
-
|
|
19
|
-
### Output Format
|
|
20
|
-
|
|
21
|
-
- **Overview**: Brief introduction to the topic
|
|
22
|
-
- **Key Findings**: Main discoveries from research
|
|
23
|
-
- **Different Perspectives**: Any varying viewpoints found
|
|
24
|
-
- **Sources**: List the URLs used with brief descriptions
|
|
25
|
-
- **Recommendations**: Suggested next steps or additional resources
|
|
26
|
-
|
|
27
|
-
Be thorough but focused. Prioritize accuracy and cite sources.
|
|
@@ -1,25 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: summarize
|
|
3
|
-
description: Summarize content from URLs, documents, or text. Use when the user wants a quick summary of something.
|
|
4
|
-
argument-hint: [url or text]
|
|
5
|
-
allowed-tools: web_fetch, read
|
|
6
|
-
---
|
|
7
|
-
|
|
8
|
-
## Instructions
|
|
9
|
-
|
|
10
|
-
Summarize the following content: $ARGUMENTS
|
|
11
|
-
|
|
12
|
-
### Steps
|
|
13
|
-
|
|
14
|
-
1. If the input is a URL, fetch the content using web_fetch
|
|
15
|
-
2. If the input is a file path, read the file
|
|
16
|
-
3. Otherwise, treat the input as text to summarize
|
|
17
|
-
|
|
18
|
-
### Output Format
|
|
19
|
-
|
|
20
|
-
Provide a summary with:
|
|
21
|
-
- **TL;DR**: One sentence summary
|
|
22
|
-
- **Key Points**: 3-5 bullet points of the main ideas
|
|
23
|
-
- **Notable Details**: Any important specifics worth highlighting
|
|
24
|
-
|
|
25
|
-
Keep the summary concise but comprehensive. Adapt the length based on the source content.
|
package/dist/config/hooks.json
DELETED
|
@@ -1,43 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"llm": {
|
|
3
|
-
"provider": "anthropic",
|
|
4
|
-
"model": "claude-opus-4-5-20251101",
|
|
5
|
-
"maxTokens": 8192
|
|
6
|
-
},
|
|
7
|
-
"voice": {
|
|
8
|
-
"enabled": false,
|
|
9
|
-
"stt": {
|
|
10
|
-
"provider": "whisper",
|
|
11
|
-
"model": "whisper-1",
|
|
12
|
-
"language": "en"
|
|
13
|
-
},
|
|
14
|
-
"tts": {
|
|
15
|
-
"provider": "elevenlabs",
|
|
16
|
-
"voiceId": "",
|
|
17
|
-
"model": "eleven_turbo_v2_5"
|
|
18
|
-
}
|
|
19
|
-
},
|
|
20
|
-
"connectors": [
|
|
21
|
-
"anthropic",
|
|
22
|
-
"brandsight",
|
|
23
|
-
"clickbank",
|
|
24
|
-
"cloudflare",
|
|
25
|
-
"discord",
|
|
26
|
-
"gmail",
|
|
27
|
-
"googlecalendar",
|
|
28
|
-
"googlecontacts",
|
|
29
|
-
"googledrive",
|
|
30
|
-
"linear",
|
|
31
|
-
"maropost",
|
|
32
|
-
"mercury",
|
|
33
|
-
"mistral",
|
|
34
|
-
"notion",
|
|
35
|
-
"openai",
|
|
36
|
-
"perplexity",
|
|
37
|
-
"sedo",
|
|
38
|
-
"slack",
|
|
39
|
-
"x",
|
|
40
|
-
"xai",
|
|
41
|
-
"zendesk"
|
|
42
|
-
]
|
|
43
|
-
}
|