@josephyan/qingflow-app-user-mcp 0.2.0-beta.33 → 0.2.0-beta.34
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/README.md
CHANGED
|
@@ -3,13 +3,13 @@
|
|
|
3
3
|
Install:
|
|
4
4
|
|
|
5
5
|
```bash
|
|
6
|
-
npm install @josephyan/qingflow-app-user-mcp@0.2.0-beta.
|
|
6
|
+
npm install @josephyan/qingflow-app-user-mcp@0.2.0-beta.34
|
|
7
7
|
```
|
|
8
8
|
|
|
9
9
|
Run:
|
|
10
10
|
|
|
11
11
|
```bash
|
|
12
|
-
npx -y -p @josephyan/qingflow-app-user-mcp@0.2.0-beta.
|
|
12
|
+
npx -y -p @josephyan/qingflow-app-user-mcp@0.2.0-beta.34 qingflow-app-user-mcp
|
|
13
13
|
```
|
|
14
14
|
|
|
15
15
|
Environment:
|
package/package.json
CHANGED
package/pyproject.toml
CHANGED
|
@@ -140,6 +140,12 @@ Top-level arguments:
|
|
|
140
140
|
- Otherwise → `初步观察`
|
|
141
141
|
- `rows_truncated=true` → 用 `前 N 个分组`, 不用 `全部`/`所有`
|
|
142
142
|
|
|
143
|
+
## Feedback Escalation
|
|
144
|
+
|
|
145
|
+
- If the desired analysis still cannot be completed because of missing capability, unsupported analysis shape, or an obviously awkward workflow after reasonable attempts, summarize the exact gap.
|
|
146
|
+
- Ask whether the user wants you to submit product feedback.
|
|
147
|
+
- Only after explicit user confirmation, call `feedback_submit`.
|
|
148
|
+
|
|
143
149
|
## Resources
|
|
144
150
|
|
|
145
151
|
- DSL templates: [references/dsl-templates.md](references/dsl-templates.md)
|
|
@@ -126,6 +126,12 @@ The DSL is clause-shaped like SQL, but it is **not raw SQL text**.
|
|
|
126
126
|
- Prefer canonical schema titles and aliases in your final wording
|
|
127
127
|
- If only part of the requested work is completed, explicitly disclose which parts are done and which are not
|
|
128
128
|
|
|
129
|
+
## Feedback Escalation
|
|
130
|
+
|
|
131
|
+
- If record CRUD still cannot satisfy the request because of missing capability, unsupported field behavior, or an obviously awkward workflow after reasonable attempts, summarize the exact blocker.
|
|
132
|
+
- Ask whether the user wants you to submit product feedback.
|
|
133
|
+
- Only after explicit user confirmation, call `feedback_submit`.
|
|
134
|
+
|
|
129
135
|
## Resources
|
|
130
136
|
|
|
131
137
|
- Record operation patterns: [references/record-patterns.md](references/record-patterns.md)
|
|
@@ -98,6 +98,12 @@ Use exactly one of these default paths:
|
|
|
98
98
|
- Avoid actions on ambiguous tasks or records
|
|
99
99
|
- Summarize the final action and the exact `app_key / record_id / workflow_node_id`
|
|
100
100
|
|
|
101
|
+
## Feedback Escalation
|
|
102
|
+
|
|
103
|
+
- If task capabilities, associated report detail, workflow log visibility, or action support still cannot satisfy the user's goal after reasonable use of this skill, summarize the exact gap in plain language.
|
|
104
|
+
- Ask whether the user wants you to submit product feedback.
|
|
105
|
+
- Only after explicit user confirmation, call `feedback_submit`.
|
|
106
|
+
|
|
101
107
|
## Response Interpretation
|
|
102
108
|
|
|
103
109
|
- `task_list` returns normalized todo rows and is the only default discovery path
|