@drunkcoding/agents-and-skills 0.0.41 → 0.0.42

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.
Files changed (9) hide show
  1. package/.claude-plugin/marketplace.json +5 -5
  2. package/package.json +1 -1
  3. package/plugins/html-effectiveness/.claude-plugin/plugin.json +1 -1
  4. package/plugins/multica-tool/.claude-plugin/plugin.json +1 -1
  5. package/plugins/multica-tool/skills/export/SKILL.md +18 -4
  6. package/plugins/multica-tool/skills/import/SKILL.md +7 -2
  7. package/plugins/plugin-validator/.claude-plugin/plugin.json +1 -1
  8. package/plugins/team-share/.claude-plugin/plugin.json +1 -1
  9. package/plugins/tech-graph/.claude-plugin/plugin.json +1 -1
package/.claude-plugin/marketplace.json CHANGED
@@ -12,7 +12,7 @@
12
12
  "name": "tech-graph",
13
13
  "source": "./plugins/tech-graph",
14
14
  "description": "6-step wizard for technical diagrams (SVG/PNG) via fireworks-tech-graph",
15
- "version": "0.0.41",
15
+ "version": "0.0.42",
16
16
  "category": "diagram",
17
17
  "keywords": [
18
18
  "diagram",
@@ -26,7 +26,7 @@
26
26
  "name": "html-effectiveness",
27
27
  "source": "./plugins/html-effectiveness",
28
28
  "description": "Generate self-contained interactive HTML reports from 20 upstream templates via a conversational agent.",
29
- "version": "0.0.41",
29
+ "version": "0.0.42",
30
30
  "category": "reports",
31
31
  "keywords": [
32
32
  "html",
@@ -41,7 +41,7 @@
41
41
  "name": "plugin-validator",
42
42
  "source": "./plugins/plugin-validator",
43
43
  "description": "Orchestrated validator for Claude Code plugins — validates skills, agents, commands, and hooks across every plugin under plugins/**.",
44
- "version": "0.0.41",
44
+ "version": "0.0.42",
45
45
  "category": "tooling",
46
46
  "keywords": [
47
47
  "validation",
@@ -57,7 +57,7 @@
57
57
  "name": "team-share",
58
58
  "source": "./plugins/team-share",
59
59
  "description": "Onboard your team with an interactive setup menu: install CodeGraph, build the Understand-Anything knowledge graph, and share Claude Code settings — run any combination, all idempotent.",
60
- "version": "0.0.41",
60
+ "version": "0.0.42",
61
61
  "category": "tooling",
62
62
  "keywords": [
63
63
  "onboarding",
@@ -73,7 +73,7 @@
73
73
  "name": "multica-tool",
74
74
  "source": "./plugins/multica-tool",
75
75
  "description": "Export, import, and sync Multica skills, agents, and squads between workspaces.",
76
- "version": "0.0.41",
76
+ "version": "0.0.42",
77
77
  "category": "workflow",
78
78
  "keywords": [
79
79
  "multica",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@drunkcoding/agents-and-skills",
3
- "version": "0.0.41",
3
+ "version": "0.0.42",
4
4
  "description": "Personal collection of Claude Code skills and agents, installable via `npx skills`.",
5
5
  "keywords": [
6
6
  "claude-code",
package/plugins/html-effectiveness/.claude-plugin/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "html-effectiveness",
3
3
  "displayName": "HTML Effectiveness Reports",
4
- "version": "0.0.41",
4
+ "version": "0.0.42",
5
5
  "description": "Generate self-contained interactive HTML reports from 20 upstream templates via a conversational agent.",
6
6
  "author": {
7
7
  "name": "Steven Hoang"
package/plugins/multica-tool/.claude-plugin/plugin.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "multica-tool",
3
- "version": "0.0.41",
3
+ "version": "0.0.42",
4
4
  "description": "Export, import, and sync Multica skills, agents, and squads between workspaces via the multica CLI."
5
5
  }
package/plugins/multica-tool/skills/export/SKILL.md CHANGED
@@ -32,13 +32,27 @@ Ask the user to select a resource by name. Resolve its `id` from the list output
32
32
 
33
33
  ## Step 3 — Determine output directory
34
34
 
35
- If the user specified an output directory, use it. Otherwise default to:
35
+ If the user specified an output directory, use it verbatim. Otherwise default to a workspace-rooted path.
36
36
 
37
+ First resolve `<workspace-name>`:
38
+
39
+ - If the user named a source workspace (the value you would pass as `--workspace <name>`), use that name.
40
+ - Otherwise, read the current default workspace's name:
41
+
42
+ ```bash
43
+ multica workspace get --output json
37
44
  ```
38
- ./multica-export-<slug>-<type>
39
- ```
40
45
 
41
- where `<slug>` is a lowercased, hyphenated form of the resource name.
46
+ and take its `.name`.
47
+
48
+ Slugify the resolved name for filesystem safety — lowercase it, replace each run of non-`[a-z0-9]` characters with a single `-`, and trim leading/trailing `-` (the same rule the scripts use internally).
49
+
50
+ Then construct the default directory by scope:
51
+
52
+ - `all` or `projects` (whole workspace) → `export/<workspace-name>`
53
+ - a single resource (`skill`, `agent`, `squad`, or `project`) → `export/<workspace-name>/<slug>-<type>`, where `<slug>` is the slugified resource name and `<type>` is the resource type.
54
+
55
+ Examples: `export all from mx-workspace` → `export/mx-workspace`; `export skill "Foo Bar" from mx-workspace` → `export/mx-workspace/foo-bar-skill`.
42
56
 
43
57
  ## Step 4 — Run the export
44
58
 
package/plugins/multica-tool/skills/import/SKILL.md CHANGED
@@ -8,9 +8,14 @@ allowed-tools: Bash, Read
8
8
 
9
9
  Import a local Multica bundle (produced by the export skill) into a target workspace.
10
10
 
11
- ## Step 1 — Confirm the target workspace
11
+ ## Step 1 — Determine the target workspace
12
12
 
13
- Ask the user to confirm the name of the target workspace if not already stated. You will need the exact workspace name as registered in Multica.
13
+ You need the exact workspace name as registered in Multica for `--workspace` in the steps below.
14
+
15
+ - If the user named a target workspace, use it.
16
+ - If the user did **not** name one, default to the **basename of the import folder** — e.g. importing from `export/mx-workspace` defaults the target workspace to `mx-workspace`. State the inferred workspace name to the user before continuing.
17
+
18
+ No existence check is needed here: the Step 2 dry-run fails with `Unknown workspace "<name>"` if the inferred workspace is not present in the target account, at which point ask the user for the correct name.
14
19
 
15
20
  ## Step 2 — Pre-flight (dry run)
16
21
 
package/plugins/plugin-validator/.claude-plugin/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "plugin-validator",
3
3
  "displayName": "Plugin Validator",
4
- "version": "0.0.41",
4
+ "version": "0.0.42",
5
5
  "description": "Orchestrated validator for Claude Code plugins — validates skills, agents, commands, and hooks across every plugin under plugins/**.",
6
6
  "author": {
7
7
  "name": "Steven Hoang"
package/plugins/team-share/.claude-plugin/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "team-share",
3
3
  "displayName": "Team Share",
4
- "version": "0.0.41",
4
+ "version": "0.0.42",
5
5
  "description": "Onboard your team with an interactive setup menu: install CodeGraph, build the Understand-Anything knowledge graph, and share Claude Code settings — run any combination, all idempotent.",
6
6
  "author": {
7
7
  "name": "Steven Hoang"
package/plugins/tech-graph/.claude-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tech-graph",
3
- "version": "0.0.41",
3
+ "version": "0.0.42",
4
4
  "description": "Step-by-step wizard for generating technical diagrams as SVG+PNG.",
5
5
  "author": {
6
6
  "name": "steven"