@zeldrisho/pi-anthropics-skills 0.0.0 → 0.1.1
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/CHANGELOG.md +9 -1
- package/LICENSE +204 -21
- package/README.md +3 -3
- package/package.json +3 -4
- package/skills/documentation/SKILL.md +16 -43
- package/skills/documentation/evals/evals.json +23 -0
- package/skills/tech-debt/SKILL.md +24 -18
- package/skills/tech-debt/evals/evals.json +23 -0
- package/skills/testing-strategy/SKILL.md +17 -19
- package/skills/testing-strategy/evals/evals.json +23 -0
- package/licenses/SOURCES.txt +0 -2
- package/licenses/anthropics-apache-2.0.txt +0 -212
package/CHANGELOG.md
CHANGED
|
@@ -7,11 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [0.1.1] - 2026-09-23
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- Clarified that the Pi skills are substantially revised adaptations of Anthropic's engineering skills, not verbatim upstream copies.
|
|
15
|
+
- Refined skill descriptions to reduce duplicated workflow detail while preserving task-selection context.
|
|
16
|
+
|
|
10
17
|
## [0.1.0] - 2026-09-21
|
|
11
18
|
|
|
12
19
|
### Added
|
|
13
20
|
|
|
14
21
|
- `documentation`, `testing-strategy`, and `tech-debt` Pi skills from Anthropic's knowledge-work plugins
|
|
15
22
|
|
|
16
|
-
[Unreleased]: https://github.com/zeldrisho/pi-packages/compare/pi-anthropics-skills-v0.1.
|
|
23
|
+
[Unreleased]: https://github.com/zeldrisho/pi-packages/compare/pi-anthropics-skills-v0.1.1...HEAD
|
|
24
|
+
[0.1.1]: https://github.com/zeldrisho/pi-packages/compare/pi-anthropics-skills-v0.1.0...pi-anthropics-skills-v0.1.1
|
|
17
25
|
[0.1.0]: https://github.com/zeldrisho/pi-packages/releases/tag/pi-anthropics-skills-v0.1.0
|
package/LICENSE
CHANGED
|
@@ -1,21 +1,204 @@
|
|
|
1
|
-
MIT
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
1
|
+
Anthropic engineering skill adaptations are licensed under Apache-2.0. Package-authored evaluation cases are offered under MIT. Source: https://github.com/anthropics/knowledge-work-plugins/tree/93d82a54e9516d172c1d0a010c1c09d56bf9d11b/engineering/skills
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
Apache License
|
|
5
|
+
Version 2.0, January 2004
|
|
6
|
+
http://www.apache.org/licenses/
|
|
7
|
+
|
|
8
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
9
|
+
|
|
10
|
+
1. Definitions.
|
|
11
|
+
|
|
12
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
13
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
14
|
+
|
|
15
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
16
|
+
the copyright owner that is granting the License.
|
|
17
|
+
|
|
18
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
19
|
+
other entities that control, are controlled by, or are under common
|
|
20
|
+
control with that entity. For the purposes of this definition,
|
|
21
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
22
|
+
direction or management of such entity, whether by contract or
|
|
23
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
24
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
25
|
+
|
|
26
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
27
|
+
exercising permissions granted by this License.
|
|
28
|
+
|
|
29
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
30
|
+
including but not limited to software source code, documentation
|
|
31
|
+
source, and configuration files.
|
|
32
|
+
|
|
33
|
+
"Object" form shall mean any form resulting from mechanical
|
|
34
|
+
transformation or translation of a Source form, including but
|
|
35
|
+
not limited to compiled object code, generated documentation,
|
|
36
|
+
and conversions to other media types.
|
|
37
|
+
|
|
38
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
39
|
+
Object form, made available under the License, as indicated by a
|
|
40
|
+
copyright notice that is included in or attached to the work
|
|
41
|
+
(an example is provided in the Appendix below).
|
|
42
|
+
|
|
43
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
44
|
+
form, that is based on (or derived from) the Work and for which the
|
|
45
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
46
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
47
|
+
of this License, Derivative Works shall not include works that remain
|
|
48
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
49
|
+
the Work and Derivative Works thereof.
|
|
50
|
+
|
|
51
|
+
"Contribution" shall mean any work of authorship, including
|
|
52
|
+
the original version of the Work and any modifications or additions
|
|
53
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
54
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
55
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
56
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
57
|
+
means any form of electronic, verbal, or written communication sent
|
|
58
|
+
to the Licensor or its representatives, including but not limited to
|
|
59
|
+
communication on electronic mailing lists, source code control systems,
|
|
60
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
61
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
62
|
+
excluding communication that is conspicuously marked or otherwise
|
|
63
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
64
|
+
|
|
65
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
66
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
67
|
+
subsequently incorporated within the Work.
|
|
68
|
+
|
|
69
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
70
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
71
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
72
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
73
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
74
|
+
Work and such Derivative Works in Source or Object form.
|
|
75
|
+
|
|
76
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
77
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
78
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
79
|
+
(except as stated in this section) patent license to make, have made,
|
|
80
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
81
|
+
where such license applies only to those patent claims licensable
|
|
82
|
+
by such Contributor that are necessarily infringed by their
|
|
83
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
84
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
85
|
+
institute patent litigation against any entity (including a
|
|
86
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
87
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
88
|
+
or contributory patent infringement, then any patent licenses
|
|
89
|
+
granted to You under this License for that Work shall terminate
|
|
90
|
+
as of the date such litigation is filed.
|
|
91
|
+
|
|
92
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
93
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
94
|
+
modifications, and in Source or Object form, provided that You
|
|
95
|
+
meet the following conditions:
|
|
96
|
+
|
|
97
|
+
(a) You must give any other recipients of the Work or
|
|
98
|
+
Derivative Works a copy of this License; and
|
|
99
|
+
|
|
100
|
+
(b) You must cause any modified files to carry prominent notices
|
|
101
|
+
stating that You changed the files; and
|
|
102
|
+
|
|
103
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
104
|
+
that You distribute, all copyright, patent, trademark, and
|
|
105
|
+
attribution notices from the Source form of the Work,
|
|
106
|
+
excluding those notices that do not pertain to any part of
|
|
107
|
+
the Derivative Works; and
|
|
108
|
+
|
|
109
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
110
|
+
distribution, then any Derivative Works that You distribute must
|
|
111
|
+
include a readable copy of the attribution notices contained
|
|
112
|
+
within such NOTICE file, excluding those notices that do not
|
|
113
|
+
pertain to any part of the Derivative Works, in at least one
|
|
114
|
+
of the following places: within a NOTICE text file distributed
|
|
115
|
+
as part of the Derivative Works; within the Source form or
|
|
116
|
+
documentation, if provided along with the Derivative Works; or,
|
|
117
|
+
within a display generated by the Derivative Works, if and
|
|
118
|
+
wherever such third-party notices normally appear. The contents
|
|
119
|
+
of the NOTICE file are for informational purposes only and
|
|
120
|
+
do not modify the License. You may add Your own attribution
|
|
121
|
+
notices within Derivative Works that You distribute, alongside
|
|
122
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
123
|
+
that such additional attribution notices cannot be construed
|
|
124
|
+
as modifying the License.
|
|
125
|
+
|
|
126
|
+
You may add Your own copyright statement to Your modifications and
|
|
127
|
+
may provide additional or different license terms and conditions
|
|
128
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
129
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
130
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
131
|
+
the conditions stated in this License.
|
|
132
|
+
|
|
133
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
134
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
135
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
136
|
+
this License, without any additional terms or conditions.
|
|
137
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
138
|
+
the terms of any separate license agreement you may have executed
|
|
139
|
+
with Licensor regarding such Contributions.
|
|
140
|
+
|
|
141
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
142
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
143
|
+
except as required for reasonable and customary use in describing the
|
|
144
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
145
|
+
|
|
146
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
147
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
148
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
149
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
150
|
+
implied, including, without limitation, any warranties or conditions
|
|
151
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
152
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
153
|
+
appropriateness of using or redistributing the Work and assume any
|
|
154
|
+
risks associated with Your exercise of permissions under this License.
|
|
155
|
+
|
|
156
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
157
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
158
|
+
unless required by applicable law (such as deliberate and grossly
|
|
159
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
160
|
+
liable to You for damages, including any direct, indirect, special,
|
|
161
|
+
incidental, or consequential damages of any character arising as a
|
|
162
|
+
result of this License or out of the use or inability to use the
|
|
163
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
164
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
165
|
+
other commercial damages or losses), even if such Contributor
|
|
166
|
+
has been advised of the possibility of such damages.
|
|
167
|
+
|
|
168
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
169
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
170
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
171
|
+
or other liability obligations and/or rights consistent with this
|
|
172
|
+
License. However, in accepting such obligations, You may act only
|
|
173
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
174
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
175
|
+
defend, and hold each Contributor harmless for any liability
|
|
176
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
177
|
+
of your accepting any such warranty or additional liability.
|
|
178
|
+
|
|
179
|
+
END OF TERMS AND CONDITIONS
|
|
180
|
+
|
|
181
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
182
|
+
|
|
183
|
+
To apply the Apache License to your work, attach the following
|
|
184
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
185
|
+
replaced with your own identifying information. (Don't include
|
|
186
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
187
|
+
comment syntax for the file format. We also recommend that a
|
|
188
|
+
file or class name and description of purpose be included on the
|
|
189
|
+
same "printed page" as the copyright notice for easier
|
|
190
|
+
identification within third-party archives.
|
|
191
|
+
|
|
192
|
+
Copyright [yyyy] [name of copyright owner]
|
|
193
|
+
|
|
194
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
195
|
+
you may not use this file except in compliance with the License.
|
|
196
|
+
You may obtain a copy of the License at
|
|
197
|
+
|
|
198
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
199
|
+
|
|
200
|
+
Unless required by applicable law or agreed to in writing, software
|
|
201
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
202
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
203
|
+
See the License for the specific language governing permissions and
|
|
204
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# @zeldrisho/pi-anthropics-skills
|
|
2
2
|
|
|
3
|
-
Pi
|
|
3
|
+
Pi-portable adaptations of Anthropic's [`engineering` skills](https://github.com/anthropics/knowledge-work-plugins/tree/93d82a54e9516d172c1d0a010c1c09d56bf9d11b/engineering/skills): `documentation`, `testing-strategy`, and `tech-debt`. These files have since been substantially revised for Agent Skills and Pi workflows; they are not verbatim upstream copies and are not endorsed by Anthropic.
|
|
4
4
|
|
|
5
5
|
## Install
|
|
6
6
|
|
|
@@ -10,8 +10,8 @@ pi install npm:@zeldrisho/pi-anthropics-skills
|
|
|
10
10
|
pi install -l npm:@zeldrisho/pi-anthropics-skills
|
|
11
11
|
```
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Select individual skills with [Pi package filtering](../../docs/package-filtering.md). Upstream provenance and license scope are documented in [`LICENSE`](LICENSE).
|
|
14
14
|
|
|
15
15
|
## License
|
|
16
16
|
|
|
17
|
-
|
|
17
|
+
Adapted upstream material is under Apache-2.0; package-authored material is under MIT where separable. See [`LICENSE`](LICENSE) for scope and attribution.
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@zeldrisho/pi-anthropics-skills",
|
|
3
|
-
"version": "0.
|
|
4
|
-
"description": "Pi engineering skills
|
|
3
|
+
"version": "0.1.1",
|
|
4
|
+
"description": "Pi adaptations of Anthropic engineering skills, revised for Agent Skills workflows",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"documentation",
|
|
7
7
|
"pi",
|
|
@@ -14,7 +14,7 @@
|
|
|
14
14
|
"bugs": {
|
|
15
15
|
"url": "https://github.com/zeldrisho/pi-packages/issues"
|
|
16
16
|
},
|
|
17
|
-
"license": "MIT",
|
|
17
|
+
"license": "(Apache-2.0 AND MIT)",
|
|
18
18
|
"author": "Zeldris",
|
|
19
19
|
"repository": {
|
|
20
20
|
"type": "git",
|
|
@@ -23,7 +23,6 @@
|
|
|
23
23
|
},
|
|
24
24
|
"files": [
|
|
25
25
|
"skills",
|
|
26
|
-
"licenses",
|
|
27
26
|
"CHANGELOG.md"
|
|
28
27
|
],
|
|
29
28
|
"type": "module",
|
|
@@ -1,54 +1,27 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: documentation
|
|
3
|
-
description: Use this skill when writing or maintaining
|
|
3
|
+
description: Use this skill when writing or maintaining engineering documentation such as READMEs, API references, runbooks, architecture documents, or onboarding guides for a specific audience.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Technical Documentation
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
Create documentation that helps its intended reader complete a task accurately. Keep procedures and claims grounded in the project, not assumptions.
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## Workflow
|
|
11
11
|
|
|
12
|
-
|
|
12
|
+
1. Identify the reader, their goal, and the document type. For a README, optimize for first successful use; for a runbook, incident recovery; for API docs, correct integration; for architecture docs, decisions and system boundaries; for onboarding, safe completion of common tasks.
|
|
13
|
+
2. Inspect the implementation and authoritative sources (configuration, API schemas, existing docs, tests, CI). Reuse verified commands and names; mark unresolved behavior as a question rather than guessing.
|
|
14
|
+
3. Lead with the information needed to act. Order steps by dependency and include prerequisites, expected results, and failure or rollback guidance when relevant.
|
|
15
|
+
4. Include a minimal working example for interfaces or procedures. Verify syntax, paths, options, outputs, and links against available sources; do not invent API behavior.
|
|
16
|
+
5. Link to the source of truth instead of duplicating policy or reference material. Keep duplicated facts minimal and clearly scoped.
|
|
17
|
+
6. Review for the intended reader: can they find the next action, understand terminology, and distinguish required from optional steps? Remove stale, redundant, or generic text.
|
|
13
18
|
|
|
14
|
-
|
|
15
|
-
- Quick start (< 5 minutes to first success)
|
|
16
|
-
- Configuration and usage
|
|
17
|
-
- Contributing guide
|
|
19
|
+
## Useful content by document type
|
|
18
20
|
|
|
19
|
-
|
|
21
|
+
- **README:** purpose, prerequisites, quick start, configuration, common usage, and links to contribution/support guidance.
|
|
22
|
+
- **API reference:** authentication, request/response shapes, errors, pagination/limits where applicable, and runnable examples.
|
|
23
|
+
- **Runbook:** trigger/conditions, access prerequisites, ordered procedure, verification, rollback, and escalation when known.
|
|
24
|
+
- **Architecture:** context, goals, components/data flow, key decisions, trade-offs, and boundaries.
|
|
25
|
+
- **Onboarding:** environment setup, system relationships, common tasks, and verified help channels.
|
|
20
26
|
|
|
21
|
-
|
|
22
|
-
- Authentication and error codes
|
|
23
|
-
- Rate limits and pagination
|
|
24
|
-
- SDK examples
|
|
25
|
-
|
|
26
|
-
### Runbook
|
|
27
|
-
|
|
28
|
-
- When to use this runbook
|
|
29
|
-
- Prerequisites and access needed
|
|
30
|
-
- Step-by-step procedure
|
|
31
|
-
- Rollback steps
|
|
32
|
-
- Escalation path
|
|
33
|
-
|
|
34
|
-
### Architecture Doc
|
|
35
|
-
|
|
36
|
-
- Context and goals
|
|
37
|
-
- High-level design with diagrams
|
|
38
|
-
- Key decisions and trade-offs
|
|
39
|
-
- Data flow and integration points
|
|
40
|
-
|
|
41
|
-
### Onboarding Guide
|
|
42
|
-
|
|
43
|
-
- Environment setup
|
|
44
|
-
- Key systems and how they connect
|
|
45
|
-
- Common tasks with walkthroughs
|
|
46
|
-
- Who to ask for what
|
|
47
|
-
|
|
48
|
-
## Principles
|
|
49
|
-
|
|
50
|
-
1. **Write for the reader** — Who is reading this and what do they need?
|
|
51
|
-
2. **Start with the most useful information** — Don't bury the lede
|
|
52
|
-
3. **Show, don't tell** — Code examples, commands, screenshots
|
|
53
|
-
4. **Keep it current** — Outdated docs are worse than no docs
|
|
54
|
-
5. **Link, don't duplicate** — Reference other docs instead of copying
|
|
27
|
+
Adapt these lists; do not add sections that do not help the reader.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
{
|
|
2
|
+
"skill_name": "documentation",
|
|
3
|
+
"evals": [
|
|
4
|
+
{
|
|
5
|
+
"id": 1,
|
|
6
|
+
"prompt": "Update this README's quick start based on the package scripts and config. Check commands actually exist.",
|
|
7
|
+
"expected_output": "A concise README section using verified commands/config, with source paths and no invented behavior.",
|
|
8
|
+
"assertions": [
|
|
9
|
+
"Commands are verified against project files",
|
|
10
|
+
"Unverified behavior is not stated as fact"
|
|
11
|
+
]
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"id": 2,
|
|
15
|
+
"prompt": "Write an incident runbook for the service, but its rollback procedure is unclear in the docs.",
|
|
16
|
+
"expected_output": "A procedure grounded in known steps, with unknown rollback details clearly called out rather than fabricated.",
|
|
17
|
+
"assertions": [
|
|
18
|
+
"Unknown rollback details are explicit",
|
|
19
|
+
"Procedure includes verification or escalation when known"
|
|
20
|
+
]
|
|
21
|
+
}
|
|
22
|
+
]
|
|
23
|
+
}
|
|
@@ -1,33 +1,39 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: tech-debt
|
|
3
|
-
description: Use this skill when auditing technical debt
|
|
3
|
+
description: Use this skill when auditing technical debt or code health, deciding whether to refactor, or prioritizing a maintainability backlog.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Tech Debt Management
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
Build an evidence-based backlog of maintainability risks and opportunities; do not label unfamiliar or merely disliked code as debt without explaining its cost.
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## Workflow
|
|
11
|
+
|
|
12
|
+
1. Clarify the audit scope, goals, constraints, and time horizon. Inspect relevant code, tests, dependency/configuration files, operational docs, and recent history or incidents when available.
|
|
13
|
+
2. Record each candidate with a specific location or artifact, observed condition, current/potential consequence, and evidence. Separate confirmed problems from hypotheses and identify missing evidence.
|
|
14
|
+
3. Categorize candidates: code, architecture, test, dependency, documentation, or infrastructure. Describe overlap once and link related items rather than double-counting.
|
|
15
|
+
4. Estimate impact, risk, and effort using the anchors below. Explain unusual scores and note dependencies or uncertainty; do not imply numeric precision.
|
|
16
|
+
5. Prioritize changes that reduce material risk or recurring friction. Suggest a bounded first step, success/exit criteria, and a suitable phase that can fit alongside feature work.
|
|
11
17
|
|
|
12
|
-
|
|
13
|
-
| ----------------------- | ---------------------------------------------------- | ------------------------ |
|
|
14
|
-
| **Code debt** | Duplicated logic, poor abstractions, magic numbers | Bugs, slow development |
|
|
15
|
-
| **Architecture debt** | Monolith that should be split, wrong data store | Scaling limits |
|
|
16
|
-
| **Test debt** | Low coverage, flaky tests, missing integration tests | Regressions ship |
|
|
17
|
-
| **Dependency debt** | Outdated libraries, unmaintained dependencies | Security vulns |
|
|
18
|
-
| **Documentation debt** | Missing runbooks, outdated READMEs, tribal knowledge | Onboarding pain |
|
|
19
|
-
| **Infrastructure debt** | Manual deploys, no monitoring, no IaC | Incidents, slow recovery |
|
|
18
|
+
## Relative scoring (1–5)
|
|
20
19
|
|
|
21
|
-
|
|
20
|
+
- **Impact:** 1 = localized inconvenience; 3 = recurring team or user cost; 5 = major reliability, security, delivery, or business impact.
|
|
21
|
+
- **Risk:** 1 = unlikely/low consequence; 3 = plausible regression, outage, or maintenance failure; 5 = credible severe or broad harm.
|
|
22
|
+
- **Effort:** 1 = small, isolated change; 3 = several files or coordinated tests; 5 = broad redesign/migration or substantial unknowns.
|
|
22
23
|
|
|
23
|
-
|
|
24
|
+
Optional ranking score: `(impact + risk) × (6 − effort)`. Use it as a discussion aid, not an objective measure; urgency, dependencies, and confidence can override the ranking.
|
|
24
25
|
|
|
25
|
-
|
|
26
|
-
- **Risk**: What happens if we don't fix it? (1-5)
|
|
27
|
-
- **Effort**: How hard is the fix? (1-5, inverted — lower effort = higher priority)
|
|
26
|
+
## Categories
|
|
28
27
|
|
|
29
|
-
|
|
28
|
+
| Type | Examples to investigate | Typical consequence |
|
|
29
|
+
| -------------- | ------------------------------------------------- | --------------------------------- |
|
|
30
|
+
| Code | Duplication, brittle coupling, unclear invariants | Defects, slow changes |
|
|
31
|
+
| Architecture | Misplaced boundaries, unsafe data flows | Scaling or change constraints |
|
|
32
|
+
| Test | Missing critical-path checks, flaky suites | Regressions, slow feedback |
|
|
33
|
+
| Dependency | Unsupported or risky dependency versions | Security, compatibility |
|
|
34
|
+
| Documentation | Stale procedures or undocumented constraints | Onboarding and operational errors |
|
|
35
|
+
| Infrastructure | Manual recovery/deployments, missing safeguards | Incidents and recovery time |
|
|
30
36
|
|
|
31
37
|
## Output
|
|
32
38
|
|
|
33
|
-
|
|
39
|
+
Present a short summary, then prioritized items with evidence/location, category, consequence, impact/risk/effort and confidence, recommended next step, dependencies, and completion criteria. Group into practical phases. Avoid unsupported claims about coverage, vulnerabilities, or dependency status; state what needs verification.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
{
|
|
2
|
+
"skill_name": "tech-debt",
|
|
3
|
+
"evals": [
|
|
4
|
+
{
|
|
5
|
+
"id": 1,
|
|
6
|
+
"prompt": "Audit this package for technical debt. Give evidence and a practical first phase; don't just list style preferences.",
|
|
7
|
+
"expected_output": "Prioritized candidates tied to artifacts, consequences, confidence, and actionable completion criteria.",
|
|
8
|
+
"assertions": [
|
|
9
|
+
"Each finding has evidence/location and consequence",
|
|
10
|
+
"Scoring uncertainty and completion criteria are stated"
|
|
11
|
+
]
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"id": 2,
|
|
15
|
+
"prompt": "A dependency looks old. Should we replace it? We have no incident history handy.",
|
|
16
|
+
"expected_output": "The agent verifies support/security status before claiming risk, records uncertainty, and suggests a bounded next step.",
|
|
17
|
+
"assertions": [
|
|
18
|
+
"Does not claim vulnerability or unsupported status without evidence",
|
|
19
|
+
"States what needs verification"
|
|
20
|
+
]
|
|
21
|
+
}
|
|
22
|
+
]
|
|
23
|
+
}
|
|
@@ -1,33 +1,31 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: testing-strategy
|
|
3
|
-
description: Use this skill when
|
|
3
|
+
description: Use this skill when planning tests, deciding what tests to write, evaluating existing test coverage, or choosing test architecture for a software change.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Testing Strategy
|
|
7
7
|
|
|
8
|
-
|
|
8
|
+
Produce a risk-based plan grounded in the codebase and the team's ability to run and maintain tests.
|
|
9
9
|
|
|
10
|
-
##
|
|
10
|
+
## Workflow
|
|
11
11
|
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
12
|
+
1. Clarify the change, user-visible behavior, critical data, and constraints (runtime, CI time, test environment).
|
|
13
|
+
2. Inspect implementation, existing tests, test commands/configuration, and recent relevant failures if available. Identify what is already covered before proposing additions.
|
|
14
|
+
3. Trace critical paths and trust boundaries. Include expected behavior, invalid inputs, failure paths, and state/data integrity.
|
|
15
|
+
4. Choose the smallest test level that gives meaningful confidence: unit for isolated logic, integration for component boundaries, end-to-end for essential user journeys. Add contract tests where independently deployed consumers depend on an interface.
|
|
16
|
+
5. Prioritize cases by impact and likelihood; note test data/setup, dependencies, and whether each case is automated, manual, or currently blocked.
|
|
17
|
+
6. Recommend coverage targets only when tied to a risk or meaningful behavior; do not prescribe a universal percentage.
|
|
17
18
|
|
|
18
|
-
##
|
|
19
|
+
## Coverage considerations
|
|
19
20
|
|
|
20
|
-
-
|
|
21
|
-
-
|
|
22
|
-
-
|
|
23
|
-
-
|
|
21
|
+
- APIs: business rules, authorization, request/response contracts, error mapping.
|
|
22
|
+
- Data workflows: validation, transformations, idempotency, partial failure, recovery.
|
|
23
|
+
- Frontends: key interactions, accessibility, loading/error states; use visual tests only where visual regressions matter.
|
|
24
|
+
- Infrastructure: deployment/configuration smoke tests and resilience/load tests when justified by impact.
|
|
25
|
+
- Scripts and migrations: include tests when they transform important data, change permissions, or can cause costly/irreversible effects. Do not exclude work just because it is a one-off.
|
|
24
26
|
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
|
|
28
|
-
|
|
29
|
-
Skip: trivial getters/setters, framework code, one-off scripts.
|
|
27
|
+
Avoid low-value tests that only restate implementation or exercise trivial framework behavior. Prefer observable assertions over implementation details.
|
|
30
28
|
|
|
31
29
|
## Output
|
|
32
30
|
|
|
33
|
-
|
|
31
|
+
Give a prioritized plan with behavior/risk, test level, concrete cases, existing coverage/gaps, and execution constraints. Distinguish recommended tests from optional follow-up work; do not invent coverage claims or targets without repository evidence.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
{
|
|
2
|
+
"skill_name": "testing-strategy",
|
|
3
|
+
"evals": [
|
|
4
|
+
{
|
|
5
|
+
"id": 1,
|
|
6
|
+
"prompt": "Plan tests for an endpoint that updates a user's billing address. Inspect existing tests first and cover authorization and validation.",
|
|
7
|
+
"expected_output": "A prioritized, repository-grounded plan accounting for existing coverage and unauthorized access.",
|
|
8
|
+
"assertions": [
|
|
9
|
+
"Existing tests are inspected before gaps are claimed",
|
|
10
|
+
"Unauthorized access and invalid input are covered"
|
|
11
|
+
]
|
|
12
|
+
},
|
|
13
|
+
{
|
|
14
|
+
"id": 2,
|
|
15
|
+
"prompt": "This one-off migration rewrites customer identifiers and can be rerun after failure. What tests should we add?",
|
|
16
|
+
"expected_output": "Risk-based tests for correctness, idempotency, partial failure/recovery and data integrity.",
|
|
17
|
+
"assertions": [
|
|
18
|
+
"Does not exclude tests because migration is one-off",
|
|
19
|
+
"Covers rerun/idempotency and data integrity"
|
|
20
|
+
]
|
|
21
|
+
}
|
|
22
|
+
]
|
|
23
|
+
}
|
package/licenses/SOURCES.txt
DELETED
|
@@ -1,212 +0,0 @@
|
|
|
1
|
-
|
|
2
|
-
Apache License
|
|
3
|
-
Version 2.0, January 2004
|
|
4
|
-
http://www.apache.org/licenses/
|
|
5
|
-
|
|
6
|
-
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
-
|
|
8
|
-
1. Definitions.
|
|
9
|
-
|
|
10
|
-
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
-
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
-
|
|
13
|
-
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
-
the copyright owner that is granting the License.
|
|
15
|
-
|
|
16
|
-
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
-
other entities that control, are controlled by, or are under common
|
|
18
|
-
control with that entity. For the purposes of this definition,
|
|
19
|
-
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
-
direction or management of such entity, whether by contract or
|
|
21
|
-
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
-
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
-
|
|
24
|
-
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
-
exercising permissions granted by this License.
|
|
26
|
-
|
|
27
|
-
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
-
including but not limited to software source code, documentation
|
|
29
|
-
source, and configuration files.
|
|
30
|
-
|
|
31
|
-
"Object" form shall mean any form resulting from mechanical
|
|
32
|
-
transformation or translation of a Source form, including but
|
|
33
|
-
not limited to compiled object code, generated documentation,
|
|
34
|
-
and conversions to other media types.
|
|
35
|
-
|
|
36
|
-
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
-
Object form, made available under the License, as indicated by a
|
|
38
|
-
copyright notice that is included in or attached to the work
|
|
39
|
-
(an example is provided in the Appendix below).
|
|
40
|
-
|
|
41
|
-
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
-
form, that is based on (or derived from) the Work and for which the
|
|
43
|
-
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
-
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
-
of this License, Derivative Works shall not include works that remain
|
|
46
|
-
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
-
the Work and Derivative Works thereof.
|
|
48
|
-
|
|
49
|
-
"Contribution" shall mean any work of authorship, including
|
|
50
|
-
the original version of the Work and any modifications or additions
|
|
51
|
-
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
-
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
-
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
-
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
-
means any form of electronic, verbal, or written communication sent
|
|
56
|
-
to the Licensor or its representatives, including but not limited to
|
|
57
|
-
communication on electronic mailing lists, source code control systems,
|
|
58
|
-
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
-
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
-
excluding communication that is conspicuously marked or otherwise
|
|
61
|
-
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
-
|
|
63
|
-
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
-
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
-
subsequently incorporated within the Work.
|
|
66
|
-
|
|
67
|
-
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
-
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
-
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
-
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
-
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
-
Work and such Derivative Works in Source or Object form.
|
|
73
|
-
|
|
74
|
-
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
-
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
-
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
-
(except as stated in this section) patent license to make, have made,
|
|
78
|
-
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
-
where such license applies only to those patent claims licensable
|
|
80
|
-
by such Contributor that are necessarily infringed by their
|
|
81
|
-
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
-
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
-
institute patent litigation against any entity (including a
|
|
84
|
-
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
-
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
-
or contributory patent infringement, then any patent licenses
|
|
87
|
-
granted to You under this License for that Work shall terminate
|
|
88
|
-
as of the date such litigation is filed.
|
|
89
|
-
|
|
90
|
-
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
-
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
-
modifications, and in Source or Object form, provided that You
|
|
93
|
-
meet the following conditions:
|
|
94
|
-
|
|
95
|
-
(a) You must give any other recipients of the Work or
|
|
96
|
-
Derivative Works a copy of this License; and
|
|
97
|
-
|
|
98
|
-
(b) You must cause any modified files to carry prominent notices
|
|
99
|
-
stating that You changed the files; and
|
|
100
|
-
|
|
101
|
-
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
-
that You distribute, all copyright, patent, trademark, and
|
|
103
|
-
attribution notices from the Source form of the Work,
|
|
104
|
-
excluding those notices that do not pertain to any part of
|
|
105
|
-
the Derivative Works; and
|
|
106
|
-
|
|
107
|
-
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
-
distribution, then any Derivative Works that You distribute must
|
|
109
|
-
include a readable copy of the attribution notices contained
|
|
110
|
-
within such NOTICE file, excluding those notices that do not
|
|
111
|
-
pertain to any part of the Derivative Works, in at least one
|
|
112
|
-
of the following places: within a NOTICE text file distributed
|
|
113
|
-
as part of the Derivative Works; within the Source form or
|
|
114
|
-
documentation, if provided along with the Derivative Works; or,
|
|
115
|
-
within a display generated by the Derivative Works, if and
|
|
116
|
-
wherever such third-party notices normally appear. The contents
|
|
117
|
-
of the NOTICE file are for informational purposes only and
|
|
118
|
-
do not modify the License. You may add Your own attribution
|
|
119
|
-
notices within Derivative Works that You distribute, alongside
|
|
120
|
-
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
-
that such additional attribution notices cannot be construed
|
|
122
|
-
as modifying the License.
|
|
123
|
-
|
|
124
|
-
You may add Your own copyright statement to Your modifications and
|
|
125
|
-
may provide additional or different license terms and conditions
|
|
126
|
-
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
-
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
-
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
-
the conditions stated in this License.
|
|
130
|
-
|
|
131
|
-
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
-
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
-
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
-
this License, without any additional terms or conditions.
|
|
135
|
-
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
-
the terms of any separate license agreement you may have executed
|
|
137
|
-
with Licensor regarding such Contributions.
|
|
138
|
-
|
|
139
|
-
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
-
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
-
except as required for reasonable and customary use in describing the
|
|
142
|
-
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
-
|
|
144
|
-
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
-
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
-
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
-
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
-
implied, including, without limitation, any warranties or conditions
|
|
149
|
-
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
-
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
-
appropriateness of using or redistributing the Work and assume any
|
|
152
|
-
risks associated with Your exercise of permissions under this License.
|
|
153
|
-
|
|
154
|
-
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
-
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
-
unless required by applicable law (such as deliberate and grossly
|
|
157
|
-
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
-
liable to You for damages, including any direct, indirect, special,
|
|
159
|
-
incidental, or consequential damages of any character arising as a
|
|
160
|
-
result of this License or out of the use or inability to use the
|
|
161
|
-
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
-
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
-
other commercial damages or losses), even if such Contributor
|
|
164
|
-
has been advised of the possibility of such damages.
|
|
165
|
-
|
|
166
|
-
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
-
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
-
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
-
or other liability obligations and/or rights consistent with this
|
|
170
|
-
License. However, in accepting such obligations, You may act only
|
|
171
|
-
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
-
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
-
defend, and hold each Contributor harmless for any liability
|
|
174
|
-
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
-
of your accepting any such warranty or additional liability.
|
|
176
|
-
|
|
177
|
-
END OF TERMS AND CONDITIONS
|
|
178
|
-
|
|
179
|
-
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
-
|
|
181
|
-
To apply the Apache License to your work, attach the following
|
|
182
|
-
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
-
replaced with your own identifying information. (Don't include
|
|
184
|
-
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
-
comment syntax for the file format. We also recommend that a
|
|
186
|
-
file or class name and description of purpose be included on the
|
|
187
|
-
same "printed page" as the copyright notice for easier
|
|
188
|
-
identification within third-party archives.
|
|
189
|
-
|
|
190
|
-
Copyright [yyyy] [name of copyright owner]
|
|
191
|
-
|
|
192
|
-
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
-
you may not use this file except in compliance with the License.
|
|
194
|
-
You may obtain a copy of the License at
|
|
195
|
-
|
|
196
|
-
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
-
|
|
198
|
-
Unless required by applicable law or agreed to in writing, software
|
|
199
|
-
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
-
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
-
See the License for the specific language governing permissions and
|
|
202
|
-
limitations under the License.
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
Syntax-file, code seperations,code vault integeted with css definition.
|
|
206
|
-
Pre-recordec, pre-tested, elements to capture elements into Packeted-User-Relations to capture - [
|
|
207
|
-
|
|
208
|
-
pre-requisites, statements, recorded-cams
|
|
209
|
-
, cams-data
|
|
210
|
-
, data, input()
|
|
211
|
-
|
|
212
|
-
]
|