luckiest-co 1.0.35 → 1.0.37
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/.claude-plugin/marketplace.json +1 -1
- package/.claude-plugin/plugin.json +1 -1
- package/bin/bump-version.js +62 -0
- package/bin/install.js +51 -3
- package/bin/sync-plugin-repo.js +57 -0
- package/package.json +8 -2
- package/skills/luckiest-charms/SKILL.md +1 -1
- package/skills/luckiest-finish/SKILL.md +1 -1
- package/skills/luckiest-go/SKILL.md +1 -1
- package/skills/luckiest-helpers/SKILL.md +1 -1
- package/skills/luckiest-home/SKILL.md +1 -1
- package/skills/luckiest-leaderboard/SKILL.md +1 -1
- package/skills/luckiest-merge/SKILL.md +1 -1
- package/skills/luckiest-next/SKILL.md +1 -1
- package/skills/luckiest-overlaps/SKILL.md +1 -1
- package/skills/luckiest-plan/SKILL.md +1 -1
- package/skills/luckiest-skills/SKILL.md +1 -1
- package/skills/luckiest-start/SKILL.md +1 -1
- package/skills/luckiest-status/SKILL.md +1 -1
- package/skills/luckiest-updates/SKILL.md +1 -1
- package/skills/luckiest-vouch/SKILL.md +1 -1
- package/skills/luckiest-wishes/SKILL.md +1 -1
- package/commands/charms.md +0 -38
- package/commands/finish.md +0 -83
- package/commands/go.md +0 -96
- package/commands/helpers.md +0 -66
- package/commands/home.md +0 -45
- package/commands/leaderboard.md +0 -39
- package/commands/merge.md +0 -38
- package/commands/next.md +0 -53
- package/commands/overlaps.md +0 -50
- package/commands/plan.md +0 -125
- package/commands/skills.md +0 -53
- package/commands/start.md +0 -45
- package/commands/status.md +0 -67
- package/commands/updates.md +0 -47
- package/commands/vouch.md +0 -33
- package/commands/wishes.md +0 -38
package/commands/vouch.md
DELETED
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
description: Request or approve a warm intro to someone outside your tribe.
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
Output rules for this command: plain language, no em dashes, no internal terms, and end with exactly one next-step line in the form `Next: <one action> (say /next to do it)`. Every Next line, including fixed ones written below, ends with " (say /next to do it)", so the user can run it by typing /next. The server may return internal words; translate them and never show them: PLAN means plan, APPLY means go, UNIFY means finish, DRAFT means in progress, DOING means active, DONE means complete, UAT means testing, AC means requirements, HANDOFF means ready for review, skill_loop means status.
|
|
6
|
-
|
|
7
|
-
## Step 1: Figure out the intent
|
|
8
|
-
|
|
9
|
-
- If the user is asking for an intro to someone (e.g. `/luckiest vouch <targetId>`, or "I need a warm intro to X"), go to Step 2.
|
|
10
|
-
- If the user is approving a vouch someone asked them for (e.g. "approve vouch <vouchId>", or they were told about a pending vouch elsewhere), go to Step 3.
|
|
11
|
-
- If neither is clear, ask which one they mean.
|
|
12
|
-
|
|
13
|
-
## Step 2: Request a warm intro
|
|
14
|
-
|
|
15
|
-
Call the `request_vouch` tool from the luckiest MCP server with `{ targetId }`. If this request is tied to an open assist request, include `assistRequestId` too.
|
|
16
|
-
|
|
17
|
-
This asks a shared 1st-degree tribe member (someone in your direct tribe who also knows the target) to vouch for you before you can reach a 3rd-degree person directly.
|
|
18
|
-
|
|
19
|
-
Report plainly that the request was sent and who needs to approve it, if the tool response says.
|
|
20
|
-
|
|
21
|
-
## Step 3: Approve a vouch
|
|
22
|
-
|
|
23
|
-
Call the `approve_vouch` tool from the luckiest MCP server with `{ vouchId }`.
|
|
24
|
-
|
|
25
|
-
Confirm plainly that the vouch was approved and the intro can proceed.
|
|
26
|
-
|
|
27
|
-
## Step 4: Wrap up
|
|
28
|
-
|
|
29
|
-
End your response with exactly one line, nothing after it:
|
|
30
|
-
|
|
31
|
-
```
|
|
32
|
-
Next: /luckiest helpers
|
|
33
|
-
```
|
package/commands/wishes.md
DELETED
|
@@ -1,38 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
description: Your wishes balance and recent related activity.
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
Output rules for this command: plain language, no em dashes, no internal terms, and end with exactly one next-step line in the form `Next: <one action> (say /next to do it)`. Every Next line, including fixed ones written below, ends with " (say /next to do it)", so the user can run it by typing /next. The server may return internal words; translate them and never show them: PLAN means plan, APPLY means go, UNIFY means finish, DRAFT means in progress, DOING means active, DONE means complete, UAT means testing, AC means requirements, HANDOFF means ready for review, skill_loop means status.
|
|
6
|
-
|
|
7
|
-
Read `references/chart-renderer.md` before rendering any chart and follow it.
|
|
8
|
-
|
|
9
|
-
## Step 1: Get the data
|
|
10
|
-
|
|
11
|
-
Call the `overview` tool from the luckiest MCP server. Use the `wishes` balance and scan `tribePulse` for any entries whose `event` text relates to wishes (earning or spending).
|
|
12
|
-
|
|
13
|
-
## Step 2: Render the dashboard
|
|
14
|
-
|
|
15
|
-
Render one fenced code block following the chart-renderer grammar:
|
|
16
|
-
|
|
17
|
-
1. Title line: `Wishes`
|
|
18
|
-
2. Balance line: `balance X` where X is the `wishes` value from `overview`, right-aligned if paired with other numbers.
|
|
19
|
-
3. If any wish-related entries exist in `tribePulse`, list them plainly, one per line, using the raw `event` text exactly as returned. Do not invent a friendlier phrasing.
|
|
20
|
-
4. If there is no daily earn/spend history available (there is no history endpoint in this version), add this exact line: `History view coming soon.` Do not invent daily numbers, trends, or a chart of activity over time. Only render a bar chart of actual daily values if such data is actually returned by a tool; since none is available here, skip the bar chart and show the line above instead.
|
|
21
|
-
5. Footer: `→ /luckiest wishes`
|
|
22
|
-
|
|
23
|
-
Example:
|
|
24
|
-
|
|
25
|
-
```
|
|
26
|
-
Wishes
|
|
27
|
-
balance 42
|
|
28
|
-
History view coming soon.
|
|
29
|
-
→ /luckiest wishes
|
|
30
|
-
```
|
|
31
|
-
|
|
32
|
-
Use only user-facing vocabulary. Never surface PLAN, APPLY, UNIFY, DRAFT, DOING, DONE, HANDOFF, or any internal term.
|
|
33
|
-
|
|
34
|
-
## Step 3: Recommend next action
|
|
35
|
-
|
|
36
|
-
End your response with exactly one line, nothing after it:
|
|
37
|
-
|
|
38
|
-
Next: /luckiest charms
|