@cleverpeople/my-skills 1.3.3 → 1.3.4

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.
@@ -1,87 +1,87 @@
1
- # Defect Risk Analyzer
2
-
3
- ## Description
4
-
5
- Analyze testing quality metrics and determine project risk level before release.
6
-
7
- ## Purpose
8
-
9
- Provide data-driven risk assessment and release readiness recommendations.
10
-
11
- ---
12
-
13
- ## Input Schema
14
-
15
- {
16
- "project_name": "string",
17
- "total_test_cases": "number",
18
- "passed_test_cases": "number",
19
- "failed_test_cases": "number",
20
- "blocked_test_cases": "number",
21
- "test_coverage_percentage": "number",
22
- "critical_defects": "number",
23
- "major_defects": "number",
24
- "minor_defects": "number"
25
- }
26
-
27
- ### Field Description
28
-
29
- - project_name: Project identifier
30
- - total_test_cases: Total test count
31
- - passed_test_cases: Successful executions
32
- - failed_test_cases: Failed executions
33
- - blocked_test_cases: Blocked executions
34
- - test_coverage_percentage: Coverage metric
35
- - critical_defects: Critical severity defects
36
- - major_defects: Major severity defects
37
- - minor_defects: Minor severity defects
38
-
39
- ---
40
-
41
- ## Output Schema
42
-
43
- {
44
- "risk_score": "number",
45
- "risk_level": "string",
46
- "project_health": "string",
47
- "release_readiness": "string",
48
- "recommendations": [
49
- "string"
50
- ]
51
- }
52
-
53
- ### Field Description
54
-
55
- - risk_score: Risk score (0-100)
56
- - risk_level: Low, Medium, High, Critical
57
- - project_health: Overall health status
58
- - release_readiness: Ready or Not Ready
59
- - recommendations: Improvement actions
60
-
61
- ---
62
-
63
- ## Risk Levels
64
-
65
- 0-20 = Low
66
-
67
- 21-50 = Medium
68
-
69
- 51-80 = High
70
-
71
- 81-100 = Critical
72
-
73
- ---
74
-
75
- ## Example Output
76
-
77
- {
78
- "risk_score": 78,
79
- "risk_level": "High",
80
- "project_health": "At Risk",
81
- "release_readiness": "Not Ready",
82
- "recommendations": [
83
- "Resolve all critical defects",
84
- "Increase test coverage above 80%",
85
- "Retest failed test cases"
86
- ]
1
+ # Defect Risk Analyzer
2
+
3
+ ## Description
4
+
5
+ Analyze testing quality metrics and determine project risk level before release.
6
+
7
+ ## Purpose
8
+
9
+ Provide data-driven risk assessment and release readiness recommendations.
10
+
11
+ ---
12
+
13
+ ## Input Schema
14
+
15
+ {
16
+ "project_name": "string",
17
+ "total_test_cases": "number",
18
+ "passed_test_cases": "number",
19
+ "failed_test_cases": "number",
20
+ "blocked_test_cases": "number",
21
+ "test_coverage_percentage": "number",
22
+ "critical_defects": "number",
23
+ "major_defects": "number",
24
+ "minor_defects": "number"
25
+ }
26
+
27
+ ### Field Description
28
+
29
+ - project_name: Project identifier
30
+ - total_test_cases: Total test count
31
+ - passed_test_cases: Successful executions
32
+ - failed_test_cases: Failed executions
33
+ - blocked_test_cases: Blocked executions
34
+ - test_coverage_percentage: Coverage metric
35
+ - critical_defects: Critical severity defects
36
+ - major_defects: Major severity defects
37
+ - minor_defects: Minor severity defects
38
+
39
+ ---
40
+
41
+ ## Output Schema
42
+
43
+ {
44
+ "risk_score": "number",
45
+ "risk_level": "string",
46
+ "project_health": "string",
47
+ "release_readiness": "string",
48
+ "recommendations": [
49
+ "string"
50
+ ]
51
+ }
52
+
53
+ ### Field Description
54
+
55
+ - risk_score: Risk score (0-100)
56
+ - risk_level: Low, Medium, High, Critical
57
+ - project_health: Overall health status
58
+ - release_readiness: Ready or Not Ready
59
+ - recommendations: Improvement actions
60
+
61
+ ---
62
+
63
+ ## Risk Levels
64
+
65
+ 0-20 = Low
66
+
67
+ 21-50 = Medium
68
+
69
+ 51-80 = High
70
+
71
+ 81-100 = Critical
72
+
73
+ ---
74
+
75
+ ## Example Output
76
+
77
+ {
78
+ "risk_score": 78,
79
+ "risk_level": "High",
80
+ "project_health": "At Risk",
81
+ "release_readiness": "Not Ready",
82
+ "recommendations": [
83
+ "Resolve all critical defects",
84
+ "Increase test coverage above 80%",
85
+ "Retest failed test cases"
86
+ ]
87
87
  }
package/README.md CHANGED
@@ -1,17 +1,303 @@
1
- # My Skills
2
-
3
- This package contains the shared `SKILL.md` definitions for the included skills, ready to be installed and shared via npm.
4
-
5
- ## Install
6
-
7
- ```powershell
8
- npm install @cleverpeople/my-skills
9
- ```
10
-
11
- ## Included skills
12
-
13
- - `Defect-Risk-Analyzer`
14
- - `Requirement-Summarizer`
15
- - `Test-Case-Generator`
16
-
17
- After installation, the package files are available in your local `node_modules/my-skills/` folder.
1
+ # My Skills
2
+
3
+ This package contains the shared `SKILL.md` definitions for the included skills, ready to be installed and shared via npm.
4
+
5
+ ## Install
6
+
7
+ ```powershell
8
+ npm install @cleverpeople/my-skills
9
+ ```
10
+
11
+ ## Included skills
12
+
13
+ - `Defect-Risk-Analyzer`
14
+ - `Requirement-Summarizer`
15
+ - `Test-Case-Generator`
16
+
17
+ After installation, the package files are available in your local `node_modules/my-skills/` folder.
18
+
19
+ ## How to use these skills
20
+
21
+ Each skill is published as a folder containing a `SKILL.md` file with structured guidance for a Copilot-style skill. You can:
22
+
23
+ 1. Install the package with npm.
24
+ 2. Copy or reference the skill folders from `node_modules/@cleverpeople/my-skills/`.
25
+ 3. Use the `SKILL.md` definitions in compatible tooling that supports shared skill packages.
26
+ 4. Provide the required input payloads for each skill to receive the expected structured output.
27
+
28
+ ---
29
+
30
+ ## Skill 1: Defect-Risk-Analyzer
31
+
32
+ ### Description
33
+
34
+ Analyze testing quality metrics and determine project risk level before release.
35
+
36
+ ### Purpose
37
+
38
+ Provide data-driven risk assessment and release readiness recommendations.
39
+
40
+ ### Input Schema
41
+
42
+ ```json
43
+ {
44
+ "project_name": "string",
45
+ "total_test_cases": "number",
46
+ "passed_test_cases": "number",
47
+ "failed_test_cases": "number",
48
+ "blocked_test_cases": "number",
49
+ "test_coverage_percentage": "number",
50
+ "critical_defects": "number",
51
+ "major_defects": "number",
52
+ "minor_defects": "number"
53
+ }
54
+ ```
55
+
56
+ ### Field Description
57
+
58
+ - `project_name`: Project identifier
59
+ - `total_test_cases`: Total test count
60
+ - `passed_test_cases`: Successful executions
61
+ - `failed_test_cases`: Failed executions
62
+ - `blocked_test_cases`: Blocked executions
63
+ - `test_coverage_percentage`: Coverage metric
64
+ - `critical_defects`: Critical severity defects
65
+ - `major_defects`: Major severity defects
66
+ - `minor_defects`: Minor severity defects
67
+
68
+ ### Output Schema
69
+
70
+ ```json
71
+ {
72
+ "risk_score": "number",
73
+ "risk_level": "string",
74
+ "project_health": "string",
75
+ "release_readiness": "string",
76
+ "recommendations": [
77
+ "string"
78
+ ]
79
+ }
80
+ ```
81
+
82
+ ### Field Description
83
+
84
+ - `risk_score`: Risk score (0-100)
85
+ - `risk_level`: Low, Medium, High, Critical
86
+ - `project_health`: Overall health status
87
+ - `release_readiness`: Ready or Not Ready
88
+ - `recommendations`: Improvement actions
89
+
90
+ ### Risk Levels
91
+
92
+ - `0-20`: Low
93
+ - `21-50`: Medium
94
+ - `51-80`: High
95
+ - `81-100`: Critical
96
+
97
+ ### Example Output
98
+
99
+ ```json
100
+ {
101
+ "risk_score": 78,
102
+ "risk_level": "High",
103
+ "project_health": "At Risk",
104
+ "release_readiness": "Not Ready",
105
+ "recommendations": [
106
+ "Resolve all critical defects",
107
+ "Increase test coverage above 80%",
108
+ "Retest failed test cases"
109
+ ]
110
+ }
111
+ ```
112
+
113
+ ---
114
+
115
+ ## Skill 2: Requirement-Summarizer
116
+
117
+ ### Description
118
+
119
+ The Requirement Summarizer analyzes requirements and user stories, extracting key business goals, features, acceptance criteria, and risks.
120
+
121
+ ### Purpose
122
+
123
+ Transform lengthy requirement documents into concise and actionable summaries.
124
+
125
+ ### Input Schema
126
+
127
+ ```json
128
+ {
129
+ "document_title": "string",
130
+ "document_type": "string",
131
+ "requirement_text": "string",
132
+ "project_name": "string",
133
+ "author": "string",
134
+ "created_date": "datetime"
135
+ }
136
+ ```
137
+
138
+ ### Field Description
139
+
140
+ - `document_title`: Name of the requirement document
141
+ - `document_type`: BRD, FRD, User Story, Epic, etc.
142
+ - `requirement_text`: Full requirement content
143
+ - `project_name`: Associated project
144
+ - `author`: Requirement owner
145
+ - `created_date`: Document creation date
146
+
147
+ ### Output Schema
148
+
149
+ ```json
150
+ {
151
+ "summary": "string",
152
+ "business_objectives": [
153
+ "string"
154
+ ],
155
+ "key_features": [
156
+ "string"
157
+ ],
158
+ "acceptance_criteria": [
159
+ "string"
160
+ ],
161
+ "risks": [
162
+ "string"
163
+ ],
164
+ "assumptions": [
165
+ "string"
166
+ ]
167
+ }
168
+ ```
169
+
170
+ ### Field Description
171
+
172
+ - `summary`: Concise requirement overview
173
+ - `business_objectives`: Primary business goals
174
+ - `key_features`: Main system capabilities
175
+ - `acceptance_criteria`: Conditions for successful implementation
176
+ - `risks`: Potential project risks
177
+ - `assumptions`: Assumptions identified from requirements
178
+
179
+ ### Example Output
180
+
181
+ ```json
182
+ {
183
+ "summary": "Users can access dashboards after authentication.",
184
+ "business_objectives": [
185
+ "Improve visibility of production data"
186
+ ],
187
+ "key_features": [
188
+ "User Authentication",
189
+ "Dashboard Access"
190
+ ],
191
+ "acceptance_criteria": [
192
+ "User can log in successfully",
193
+ "Dashboard loads within 3 seconds"
194
+ ],
195
+ "risks": [
196
+ "Single Sign-On dependency"
197
+ ],
198
+ "assumptions": [
199
+ "Users possess valid credentials"
200
+ ]
201
+ }
202
+ ```
203
+
204
+ ---
205
+
206
+ ## Skill 3: Test-Case-Generator
207
+
208
+ ### Description
209
+
210
+ Generate test scenarios and test cases from requirements and acceptance criteria.
211
+
212
+ ### Purpose
213
+
214
+ Accelerate software testing preparation and improve test coverage.
215
+
216
+ ### Input Schema
217
+
218
+ ```json
219
+ {
220
+ "requirement_id": "string",
221
+ "requirement_title": "string",
222
+ "summary": "string",
223
+ "acceptance_criteria": [
224
+ "string"
225
+ ],
226
+ "application_type": "string",
227
+ "priority": "string"
228
+ }
229
+ ```
230
+
231
+ ### Field Description
232
+
233
+ - `requirement_id`: Unique requirement identifier
234
+ - `requirement_title`: Requirement title
235
+ - `summary`: Requirement summary
236
+ - `acceptance_criteria`: List of acceptance criteria
237
+ - `application_type`: Web, Mobile, Desktop, API
238
+ - `priority`: High, Medium, Low
239
+
240
+ ### Output Schema
241
+
242
+ ```json
243
+ {
244
+ "test_cases": [
245
+ {
246
+ "test_case_id": "string",
247
+ "title": "string",
248
+ "priority": "string",
249
+ "pre_conditions": [
250
+ "string"
251
+ ],
252
+ "test_steps": [
253
+ "string"
254
+ ],
255
+ "expected_results": [
256
+ "string"
257
+ ]
258
+ }
259
+ ]
260
+ }
261
+ ```
262
+
263
+ ### Field Description
264
+
265
+ - `test_case_id`: Unique test case identifier
266
+ - `title`: Test case title
267
+ - `priority`: Business priority
268
+ - `pre_conditions`: Required setup
269
+ - `test_steps`: Execution steps
270
+ - `expected_results`: Validation outcomes
271
+
272
+ ### Example Output
273
+
274
+ ```json
275
+ {
276
+ "test_cases": [
277
+ {
278
+ "test_case_id": "TC001",
279
+ "title": "Verify Successful Login",
280
+ "priority": "High",
281
+ "pre_conditions": [
282
+ "User account exists"
283
+ ],
284
+ "test_steps": [
285
+ "Open login page",
286
+ "Enter valid credentials",
287
+ "Click Login"
288
+ ],
289
+ "expected_results": [
290
+ "Dashboard displayed successfully"
291
+ ]
292
+ }
293
+ ]
294
+ }
295
+ ```
296
+
297
+ ---
298
+
299
+ ## Notes
300
+
301
+ - The project also includes a lightweight HTTP server in `server.js` that exposes the available skills through API endpoints.
302
+ - The `src/skill-loader.js` utility reads each skill folder and loads the content of its `SKILL.md` file.
303
+ - The package currently includes the three skills listed above and is ready to be published or shared as a reusable skill bundle.
@@ -1,88 +1,88 @@
1
- # Requirement Summarizer
2
-
3
- ## Description
4
-
5
- The Requirement Summarizer analyzes requirements and user stories, extracting key business goals, features, acceptance criteria, and risks.
6
-
7
- ## Purpose
8
-
9
- Transform lengthy requirement documents into concise and actionable summaries.
10
-
11
- ---
12
-
13
- ## Input Schema
14
-
15
- {
16
- "document_title": "string",
17
- "document_type": "string",
18
- "requirement_text": "string",
19
- "project_name": "string",
20
- "author": "string",
21
- "created_date": "datetime"
22
- }
23
-
24
- ### Field Description
25
-
26
- - document_title: Name of the requirement document
27
- - document_type: BRD, FRD, User Story, Epic, etc.
28
- - requirement_text: Full requirement content
29
- - project_name: Associated project
30
- - author: Requirement owner
31
- - created_date: Document creation date
32
-
33
- ---
34
-
35
- ## Output Schema
36
-
37
- {
38
- "summary": "string",
39
- "business_objectives": [
40
- "string"
41
- ],
42
- "key_features": [
43
- "string"
44
- ],
45
- "acceptance_criteria": [
46
- "string"
47
- ],
48
- "risks": [
49
- "string"
50
- ],
51
- "assumptions": [
52
- "string"
53
- ]
54
- }
55
-
56
- ### Field Description
57
-
58
- - summary: Concise requirement overview
59
- - business_objectives: Primary business goals
60
- - key_features: Main system capabilities
61
- - acceptance_criteria: Conditions for successful implementation
62
- - risks: Potential project risks
63
- - assumptions: Assumptions identified from requirements
64
-
65
- ---
66
-
67
- ## Example Output
68
-
69
- {
70
- "summary": "Users can access dashboards after authentication.",
71
- "business_objectives": [
72
- "Improve visibility of production data"
73
- ],
74
- "key_features": [
75
- "User Authentication",
76
- "Dashboard Access"
77
- ],
78
- "acceptance_criteria": [
79
- "User can log in successfully",
80
- "Dashboard loads within 3 seconds"
81
- ],
82
- "risks": [
83
- "Single Sign-On dependency"
84
- ],
85
- "assumptions": [
86
- "Users possess valid credentials"
87
- ]
88
- }
1
+ # Requirement Summarizer
2
+
3
+ ## Description
4
+
5
+ The Requirement Summarizer analyzes requirements and user stories, extracting key business goals, features, acceptance criteria, and risks.
6
+
7
+ ## Purpose
8
+
9
+ Transform lengthy requirement documents into concise and actionable summaries.
10
+
11
+ ---
12
+
13
+ ## Input Schema
14
+
15
+ {
16
+ "document_title": "string",
17
+ "document_type": "string",
18
+ "requirement_text": "string",
19
+ "project_name": "string",
20
+ "author": "string",
21
+ "created_date": "datetime"
22
+ }
23
+
24
+ ### Field Description
25
+
26
+ - document_title: Name of the requirement document
27
+ - document_type: BRD, FRD, User Story, Epic, etc.
28
+ - requirement_text: Full requirement content
29
+ - project_name: Associated project
30
+ - author: Requirement owner
31
+ - created_date: Document creation date
32
+
33
+ ---
34
+
35
+ ## Output Schema
36
+
37
+ {
38
+ "summary": "string",
39
+ "business_objectives": [
40
+ "string"
41
+ ],
42
+ "key_features": [
43
+ "string"
44
+ ],
45
+ "acceptance_criteria": [
46
+ "string"
47
+ ],
48
+ "risks": [
49
+ "string"
50
+ ],
51
+ "assumptions": [
52
+ "string"
53
+ ]
54
+ }
55
+
56
+ ### Field Description
57
+
58
+ - summary: Concise requirement overview
59
+ - business_objectives: Primary business goals
60
+ - key_features: Main system capabilities
61
+ - acceptance_criteria: Conditions for successful implementation
62
+ - risks: Potential project risks
63
+ - assumptions: Assumptions identified from requirements
64
+
65
+ ---
66
+
67
+ ## Example Output
68
+
69
+ {
70
+ "summary": "Users can access dashboards after authentication.",
71
+ "business_objectives": [
72
+ "Improve visibility of production data"
73
+ ],
74
+ "key_features": [
75
+ "User Authentication",
76
+ "Dashboard Access"
77
+ ],
78
+ "acceptance_criteria": [
79
+ "User can log in successfully",
80
+ "Dashboard loads within 3 seconds"
81
+ ],
82
+ "risks": [
83
+ "Single Sign-On dependency"
84
+ ],
85
+ "assumptions": [
86
+ "Users possess valid credentials"
87
+ ]
88
+ }
@@ -1,91 +1,91 @@
1
- # Test Case Generator
2
-
3
- ## Description
4
-
5
- Generate test scenarios and test cases from requirements and acceptance criteria.
6
-
7
- ## Purpose
8
-
9
- Accelerate software testing preparation and improve test coverage.
10
-
11
- ---
12
-
13
- ## Input Schema
14
-
15
- {
16
- "requirement_id": "string",
17
- "requirement_title": "string",
18
- "summary": "string",
19
- "acceptance_criteria": [
20
- "string"
21
- ],
22
- "application_type": "string",
23
- "priority": "string"
24
- }
25
-
26
- ### Field Description
27
-
28
- - requirement_id: Unique requirement identifier
29
- - requirement_title: Requirement title
30
- - summary: Requirement summary
31
- - acceptance_criteria: List of acceptance criteria
32
- - application_type: Web, Mobile, Desktop, API
33
- - priority: High, Medium, Low
34
-
35
- ---
36
-
37
- ## Output Schema
38
-
39
- {
40
- "test_cases": [
41
- {
42
- "test_case_id": "string",
43
- "title": "string",
44
- "priority": "string",
45
- "pre_conditions": [
46
- "string"
47
- ],
48
- "test_steps": [
49
- "string"
50
- ],
51
- "expected_results": [
52
- "string"
53
- ]
54
- }
55
- ]
56
- }
57
-
58
- ### Field Description
59
-
60
- - test_case_id: Unique test case identifier
61
- - title: Test case title
62
- - priority: Business priority
63
- - pre_conditions: Required setup
64
- - test_steps: Execution steps
65
- - expected_results: Validation outcomes
66
-
67
- ---
68
-
69
- ## Example Output
70
-
71
- {
72
- "test_cases": [
73
- {
74
- "test_case_id": "TC001",
75
- "title": "Verify Successful Login",
76
- "priority": "High",
77
- "pre_conditions": [
78
- "User account exists"
79
- ],
80
- "test_steps": [
81
- "Open login page",
82
- "Enter valid credentials",
83
- "Click Login"
84
- ],
85
- "expected_results": [
86
- "Dashboard displayed successfully"
87
- ]
88
- }
89
- ]
90
- }
1
+ # Test Case Generator
2
+
3
+ ## Description
4
+
5
+ Generate test scenarios and test cases from requirements and acceptance criteria.
6
+
7
+ ## Purpose
8
+
9
+ Accelerate software testing preparation and improve test coverage.
10
+
11
+ ---
12
+
13
+ ## Input Schema
14
+
15
+ {
16
+ "requirement_id": "string",
17
+ "requirement_title": "string",
18
+ "summary": "string",
19
+ "acceptance_criteria": [
20
+ "string"
21
+ ],
22
+ "application_type": "string",
23
+ "priority": "string"
24
+ }
25
+
26
+ ### Field Description
27
+
28
+ - requirement_id: Unique requirement identifier
29
+ - requirement_title: Requirement title
30
+ - summary: Requirement summary
31
+ - acceptance_criteria: List of acceptance criteria
32
+ - application_type: Web, Mobile, Desktop, API
33
+ - priority: High, Medium, Low
34
+
35
+ ---
36
+
37
+ ## Output Schema
38
+
39
+ {
40
+ "test_cases": [
41
+ {
42
+ "test_case_id": "string",
43
+ "title": "string",
44
+ "priority": "string",
45
+ "pre_conditions": [
46
+ "string"
47
+ ],
48
+ "test_steps": [
49
+ "string"
50
+ ],
51
+ "expected_results": [
52
+ "string"
53
+ ]
54
+ }
55
+ ]
56
+ }
57
+
58
+ ### Field Description
59
+
60
+ - test_case_id: Unique test case identifier
61
+ - title: Test case title
62
+ - priority: Business priority
63
+ - pre_conditions: Required setup
64
+ - test_steps: Execution steps
65
+ - expected_results: Validation outcomes
66
+
67
+ ---
68
+
69
+ ## Example Output
70
+
71
+ {
72
+ "test_cases": [
73
+ {
74
+ "test_case_id": "TC001",
75
+ "title": "Verify Successful Login",
76
+ "priority": "High",
77
+ "pre_conditions": [
78
+ "User account exists"
79
+ ],
80
+ "test_steps": [
81
+ "Open login page",
82
+ "Enter valid credentials",
83
+ "Click Login"
84
+ ],
85
+ "expected_results": [
86
+ "Dashboard displayed successfully"
87
+ ]
88
+ }
89
+ ]
90
+ }
91
91
  `
package/package.json CHANGED
@@ -1,15 +1,19 @@
1
- {
2
- "name": "@cleverpeople/my-skills",
3
- "version": "1.3.3",
4
- "private": false,
5
- "description": "Shared skill definitions bundle for My Skills.",
6
- "files": [
7
- "Defect-Risk-Analyzer",
8
- "Requirement-Summarizer",
9
- "Test-Case-Generator",
10
- "README.md"
11
- ],
12
- "publishConfig": {
13
- "access": "public"
14
- }
15
- }
1
+ {
2
+ "name": "@cleverpeople/my-skills",
3
+ "version": "1.3.4",
4
+ "private": false,
5
+ "description": "Shared skill definitions bundle for My Skills.",
6
+ "type": "module",
7
+ "scripts": {
8
+ "test": "node --test"
9
+ },
10
+ "files": [
11
+ "Defect-Risk-Analyzer",
12
+ "Requirement-Summarizer",
13
+ "Test-Case-Generator",
14
+ "README.md"
15
+ ],
16
+ "publishConfig": {
17
+ "access": "public"
18
+ }
19
+ }