@powerformer/refly-cli 0.1.16 → 0.1.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@powerformer/refly-cli",
-  "version": "0.1.16",
+  "version": "0.1.18",
   "description": "Refly CLI - Command-line interface for Refly workflow orchestration",
   "bin": {
     "refly": "./dist/bin/refly.js"
@@ -9,6 +9,7 @@
   "types": "dist/index.d.ts",
   "scripts": {
     "build": "tsup",
+    "build:dev": "REFLY_BUILD_ENV=dev tsup",
     "build:test": "REFLY_BUILD_ENV=test tsup",
     "build:staging": "REFLY_BUILD_ENV=staging tsup",
     "build:prod": "REFLY_BUILD_ENV=production tsup",

package/skill/SKILL.md

@@ -2,7 +2,7 @@
 name: refly
 description: |
   Base skill for Refly ecosystem: creates, discovers, and runs domain-specific skills bound to workflows.
-  Routes user intent to matching domain skills via local registry, delegates execution to Refly backend.
+  Routes user intent to matching domain skills via symlinks in ~/.claude/skills/, delegates execution to Refly backend.
   Use when user asks to: create skills, run workflows, automate multi-step tasks, or manage pipelines.
   Triggers: refly, skill, workflow, run skill, create skill, automation, pipeline.
   Requires: @refly/cli installed and authenticated.
@@ -33,28 +33,30 @@ Tip: Get `installationId` from `refly skill installations` after installing a sk
 ## Directory Structure
 
 ```
-~/.claude/skills/refly/
-|-- SKILL.md                    # Base skill (this file)
-|-- registry.json               # Routing registry
-|-- references/                 # Core CLI docs
-|   |-- workflow.md
-|   |-- node.md
-|   |-- file.md
-|   `-- skill.md
-`-- domain-skills/              # Domain skills (one directory per skill)
-    `-- <skill-name>/
-        |-- skill.md            # Entry file
-        `-- ...                 # Additional docs
+~/.refly/skills/
+├── base/                       # Base skill files (this symlink target)
+│   ├── SKILL.md
+│   └── rules/
+│       ├── workflow.md
+│       ├── node.md
+│       ├── file.md
+│       └── skill.md
+└── <skill-name>/               # Domain skill directories
+    └── SKILL.md
+
+~/.claude/skills/
+├── refly → ~/.refly/skills/base/           # Base skill symlink
+└── <skill-name> → ~/.refly/skills/<name>/  # Domain skill symlinks
 ```
 
 ## Routing
 
-User intent -> match domain skill (name/trigger/description) -> read domain skill `.md`
--> execute via `refly skill run` -> return CLI-verified result.
+User intent -> match domain skill (name/trigger) in `~/.claude/skills/`
+-> read domain skill `SKILL.md` -> execute via `refly skill run` -> return CLI-verified result.
 
 ## References
 
-- `references/workflow.md` - Workflow command reference
-- `references/node.md` - Node command reference
-- `references/file.md` - File command reference
-- `references/skill.md` - Customized Skill command reference
+- `rules/workflow.md` - Workflow command reference
+- `rules/node.md` - Node command reference
+- `rules/file.md` - File command reference
+- `rules/skill.md` - Customized Skill command reference

package/skill/references/skill.md

@@ -200,70 +200,34 @@ CLI will return `skill.create.needs_workflow` with suggested options and example
 ## Directory Structure
 
 ```
-~/.claude/skills/refly/
-|-- SKILL.md                    # Base skill
-|-- registry.json               # Skill index
-|-- references/                 # Core CLI docs
-|   |-- workflow.md
-|   |-- node.md
-|   |-- file.md
-|   `-- skill.md
-`-- domain-skills/              # Domain skills (one directory per skill)
-    `-- <skill-name>/
-        |-- skill.md            # Entry file
-        |-- REFERENCE.md        # API reference (optional)
-        `-- EXAMPLES.md         # Examples (optional)
+~/.refly/skills/
+├── base/                       # Base skill files (symlink target for 'refly')
+│   ├── SKILL.md
+│   └── rules/
+│       ├── workflow.md
+│       ├── node.md
+│       ├── file.md
+│       └── skill.md
+└── <skill-name>/               # Domain skill directories
+    └── SKILL.md
+
+~/.claude/skills/
+├── refly → ~/.refly/skills/base/           # Base skill symlink
+└── <skill-name> → ~/.refly/skills/<name>/  # Domain skill symlinks
 ```
 
----
-
-## Registry Schema
+### How Symlinks Work
 
-```json
-{
-  "version": 1,
-  "updatedAt": "2025-01-14T00:00:00Z",
-  "skills": [
-    {
-      "name": "pdf-processing",
-      "description": "Extract text/tables from PDF, fill forms, merge documents.",
-      "workflowId": "c-abc123xyz",
-      "triggers": ["pdf extract", "process pdf", "fill pdf form"],
-      "path": "domain-skills/pdf-processing",
-      "createdAt": "2025-01-14T00:00:00Z",
-      "updatedAt": "2025-01-14T00:00:00Z",
-      "source": "local",
-      "tags": ["pdf", "document"],
-      "author": "team-refly",
-      "version": "1.0.0",
-      "skillId": "skp-abc123"
-    }
-  ]
-}
-```
+- **Base skill**: `~/.claude/skills/refly` → `~/.refly/skills/base/`
+- **Domain skills**: `~/.claude/skills/<name>` → `~/.refly/skills/<name>/`
 
-### Registry Fields
-
-| Field | Type | Required | Description |
-|------|------|----------|-------------|
-| name | string | Yes | Unique skill identifier (lowercase, hyphens) |
-| description | string | Yes | One-line summary for matching |
-| workflowId | string | Yes | Bound workflow ID in Refly backend |
-| triggers | string[] | Yes | Phrases that trigger this skill |
-| path | string | Yes | Relative path to skill directory |
-| createdAt | string | Yes | ISO 8601 timestamp |
-| source | string | Yes | `local` or `refly-cloud` |
-| updatedAt | string | No | ISO 8601 timestamp |
-| tags | string[] | No | Categorization tags |
-| author | string | No | Skill author |
-| version | string | No | Semantic version |
-| skillId | string | No | Cloud skill ID (if available) |
+Claude Code discovers skills via symlinks in `~/.claude/skills/`. Each skill is a symlink pointing to the actual skill directory in `~/.refly/skills/`.
 
 ---
 
 ## Domain Skill Template
 
-Location: `~/.claude/skills/refly/domain-skills/<skill-name>/skill.md`
+Location: `~/.refly/skills/<skill-name>/SKILL.md` (accessed via `~/.claude/skills/<skill-name>/SKILL.md`)
 
 ````markdown
 ---
@@ -323,14 +287,14 @@ refly skill run <installationId> --input '<json>'
 
 | Type | Location | Management | Use Case |
 |------|----------|------------|----------|
-| Local | `~/.claude/skills/refly/domain-skills/` | `registry.json` | Fast iteration |
+| Local | `~/.refly/skills/<name>/` | Symlinks | Fast iteration |
 | Cloud | Backend `SkillPackage` | API | Distribution & versioning |
 
 Integration flow:
-1. Write local `skill.md` -> run `refly skill sync` -> updates `registry.json`
-2. Create cloud skill -> `refly skill create` (bind workflow) -> `refly skill publish`
-3. Install to run -> `refly skill install` -> `refly skill run <installationId>`
-4. Cloud skills can still match locally via `source: refly-cloud`
+1. Create cloud skill -> `refly skill create` (generates workflow + local symlink)
+2. Publish skill -> `refly skill publish` -> makes skill discoverable
+3. Install to run -> `refly skill install` -> creates local SKILL.md + symlink
+4. Run skill -> `refly skill run <installationId>`
 
 ---
 
@@ -419,10 +383,11 @@ Integration flow:
 ## Skill Sync Details
 
 `refly skill sync` will:
-- Scan local `domain-skills/` directories
-- Load frontmatter from each `skill.md`
-- Update `registry.json` with added/updated entries
-- Optionally prune orphan entries with `--prune`
+- Validate existing symlinks in `~/.claude/skills/`
+- Check for broken symlinks (pointing to non-existent directories)
+- Check for orphan directories (directories without symlinks)
+- With `--fix`: recreate broken symlinks
+- With `--prune`: remove broken symlinks
 
 ---
 

package/skill/registry.json

@@ -1,15 +0,0 @@
-{
-  "version": 1,
-  "updatedAt": "2025-01-14T00:00:00Z",
-  "skills": [
-    {
-      "name": "pdf-processing",
-      "description": "从 PDF 文件中提取文本和表格、填充表单、合并文档。在处理 PDF 文件或用户提及 PDF、表单或文档提取时使用。",
-      "workflowId": "wf_pdf_processing_v1",
-      "triggers": ["pdf extract", "pdf 提取", "处理 pdf", "fill pdf form"],
-      "path": "domain-skills/pdf-processing/",
-      "createdAt": "2025-01-14T00:00:00Z",
-      "source": "local"
-    }
-  ]
-}