@powerformer/refly-cli 0.1.13 → 0.1.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@powerformer/refly-cli",
-  "version": "0.1.13",
+  "version": "0.1.15",
   "description": "Refly CLI - Command-line interface for Refly workflow orchestration",
   "bin": {
     "refly": "./dist/bin/refly.js"
@@ -23,6 +23,9 @@
   "license": "MIT",
   "dependencies": {
     "commander": "^12.1.0",
+    "form-data": "^4.0.1",
+    "gray-matter": "^4.0.3",
+    "mime": "^4.0.4",
     "zod": "^3.23.8",
     "open": "^10.1.0"
   },

package/skill/SKILL.md

@@ -24,34 +24,37 @@ description: |
 refly status
 refly login
 refly skill list
-refly skill run <name> --input '<json>'
+refly skill installations
+refly skill run <installationId> --input '<json>'
 ```
 
+Tip: Get `installationId` from `refly skill installations` after installing a skill.
+
 ## 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
+|-- 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
 ```
 
 ## 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/description) -> read domain skill `.md`
+-> execute via `refly skill run` -> return CLI-verified result.
 
 ## References
 
-- `references/workflow.md`
-- `references/node.md`
-- `references/file.md`
-- `references/skill.md`
+- `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

package/skill/references/file.md

@@ -3,18 +3,30 @@
 ## File Commands
 
 ```bash
-refly file list
-refly file list --canvas-id <id>
-refly file get <fileId>
-refly file download <fileId> -o ./output.txt
+# List files
+refly file list [options]
+  --page <n>           # Page number (default: 1)
+  --page-size <n>      # Files per page (default: 20)
+  --canvas-id <id>     # Filter by canvas ID
+  --result-id <id>     # Filter by action result ID
+  --include-content    # Include file content in response
+
+# Get file details
+refly file get <fileId> [options]
+  --no-content         # Exclude file content
+
+# Download file
+refly file download <fileId> [options]
+  -o, --output <path>  # Output path (defaults to original filename)
+
+# Upload file(s)
+refly file upload <path> [options]
+  --canvas-id <id>     # Canvas ID (required)
+  --filter <ext>       # Filter by extensions (e.g., pdf,docx,png)
 ```
 
 ## Interaction
 
 - File IDs typically come from action results (`node.md`) or workflow outputs (`workflow.md`).
 - Use file commands to retrieve content produced by workflow runs.
-
-## Backend API (File)
-
-- GET /v1/cli/file list files
-- GET /v1/cli/file/:id get file
+- Use `--result-id` or `--canvas-id` to narrow file listings to a specific run context.

package/skill/references/node.md

@@ -1,63 +1,87 @@
 # Node Reference
 
-## Node Commands
+## Node Types
+
+Examples below use two common node types:
+- `start` - Workflow entry point that captures user input
+- `skillResponse` - AI-powered response node that can use tools
+
+## Node Execution Commands
+
+Node execution commands are now under `refly workflow run`:
 
 ```bash
-refly node types
-refly node run --type "<nodeType>" --input '<json>'
-refly node result <resultId>
-refly node result <resultId> --include-tool-calls
-refly node result <resultId> --include-steps
-refly node result <resultId> --include-messages
-refly node abort <resultId>
+# Run From Here (from this node + downstream nodes)
+refly workflow run node-start [options]
+  --from <nodeId>            # Node to run from (includes downstream)
+  --run-id <runId>           # Existing run context
+  --workflow-id <id>         # Start new run from workflow
+
+# Abort running node
+refly workflow run node-abort <resultId> [options]
+  --version <number>         # Specific version to abort
+
+# Get node execution result
+refly workflow run node-result <resultId> [options]
+  --include-steps            # Include step details
+  --include-messages         # Include chat messages
+  --include-tool-calls       # Include tool call details
+
+# Get node detail within a workflow run
+refly workflow run node-detail <runId> <nodeId> [options]
+  --include-messages         # Include AI messages
+  --raw                      # Disable output sanitization
+
+# List tool calls from node execution
+refly workflow run node-toolcalls <resultId> [options]
+  --status <status>          # Filter: executing, completed, failed
+  --tool-name <name>         # Filter by tool name
+  --toolset-id <id>          # Filter by toolset ID
+
+# Single tool call detail
+refly workflow run node-toolcall <callId> [options]
+  --raw                      # Full output without sanitization
 ```
 
+Note: Use `--run-id` when you already have a specific run context; use `--workflow-id` to start a new run from a node.
+
 ## List Nodes in Workflow
 
 ```bash
-refly workflow nodes <workflowId>
-refly workflow nodes <workflowId> --include-edges
-refly workflow nodes <workflowId> --include-metadata
+refly workflow nodes <workflowId> [options]
+  --include-edges            # Include edge/connection info
+  --include-position         # Include node coordinates
+  --include-metadata         # Include full node metadata
 ```
 
 ## Get Single Node Information
 
 ```bash
-refly workflow node <workflowId> <nodeId>
-refly workflow node <workflowId> <nodeId> --include-connections
+refly workflow node <id> <nodeId> [options]
+  --include-connections      # Include incoming/outgoing connections
 ```
 
+Note: `<id>` can be workflow ID (`c-xxx`) or run ID (`we-xxx`).
+
 ## Interaction
 
-- `workflow run node <runId> <nodeId>` yields `resultId` used by node/tool commands.
-- Use `node result` to fetch node output and optional file IDs.
-- Use `tool calls` to inspect tool executions tied to a result.
+- `workflow run node-detail <runId> <nodeId>` yields `resultId` used by node/tool commands.
+- Use `workflow run node-result` to fetch node output and optional file IDs.
+- Use `workflow run node-toolcalls` to inspect tool execution details.
 - File IDs from node results should be handled via `file.md`.
 
-## Node Result Commands
-
-```bash
-refly node result <resultId>
-refly node result <resultId> --include-steps
-refly node result <resultId> --include-messages
-refly node result <resultId> --include-tool-calls
-```
-
-## Tool Commands
-
-```bash
-refly tool calls --result-id <resultId>
-refly tool get <callId>
-```
-
-## Backend API (Node)
+## Migration Note
 
-- GET /v1/cli/node/types list node types
-- POST /v1/cli/node/run run a single node (not implemented yet)
-- GET /v1/cli/action/result?resultId=<id> get node execution result
-- POST /v1/cli/action/abort abort node execution
+The following commands have been migrated:
 
-## Backend API (Tool)
+| Old Command | New Command |
+|-------------|-------------|
+| `refly node run --type <t>` | **REMOVED** - Use `refly workflow run node-start --type <t>` |
+| `refly node result <id>` | `refly workflow run node-result <id>` |
+| `refly node abort <id>` | `refly workflow run node-abort <resultId>` |
+| `refly workflow run node <runId> <nodeId>` | `refly workflow run node-detail <runId> <nodeId>` |
 
-- GET /v1/cli/toolcall?resultId=<id>&version=<n> tool calls for action result
-- GET /v1/cli/toolcall/:callId single tool call detail
+**Breaking Change:** The standalone `refly node` command group has been removed.
+Node execution is now under `refly workflow run node-*`. For single-node debugging, use:
+1. `refly workflow run node-start --type <t>`
+2. Use `node-start --from <nodeId> --run-id <runId>` to run from node + downstream