devlyn-cli 0.0.6 → 0.0.7
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 +1 -0
- package/bin/devlyn.js +1 -0
- package/optional-skills/pyx-scan/SKILL.md +185 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -96,6 +96,7 @@ During installation, you can choose to add optional skills and third-party skill
|
|
|
96
96
|
|---|---|---|
|
|
97
97
|
| `cloudflare-nextjs-setup` | skill | Cloudflare Workers + Next.js deployment with OpenNext |
|
|
98
98
|
| `prompt-engineering` | skill | Claude 4 prompt optimization using Anthropic best practices |
|
|
99
|
+
| `pyx-scan` | skill | Check whether an AI agent skill is safe before installing |
|
|
99
100
|
| `vercel-labs/agent-skills` | pack | React, Next.js, React Native best practices |
|
|
100
101
|
| `supabase/agent-skills` | pack | Supabase integration patterns |
|
|
101
102
|
| `coreyhaines31/marketingskills` | pack | Marketing automation and content skills |
|
package/bin/devlyn.js
CHANGED
|
@@ -61,6 +61,7 @@ const OPTIONAL_ADDONS = [
|
|
|
61
61
|
// Local optional skills (copied to .claude/skills/)
|
|
62
62
|
{ name: 'cloudflare-nextjs-setup', desc: 'Cloudflare Workers + Next.js deployment with OpenNext', type: 'local' },
|
|
63
63
|
{ name: 'prompt-engineering', desc: 'Claude 4 prompt optimization using Anthropic best practices', type: 'local' },
|
|
64
|
+
{ name: 'pyx-scan', desc: 'Check whether an AI agent skill is safe before installing', type: 'local' },
|
|
64
65
|
// External skill packs (installed via npx skills add)
|
|
65
66
|
{ name: 'vercel-labs/agent-skills', desc: 'React, Next.js, React Native best practices', type: 'external' },
|
|
66
67
|
{ name: 'supabase/agent-skills', desc: 'Supabase integration patterns', type: 'external' },
|
|
@@ -0,0 +1,185 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: pyx-scan
|
|
3
|
+
description: >
|
|
4
|
+
Check whether an AI agent skill is safe before installing or using it.
|
|
5
|
+
Calls the PYX Scanner API to retrieve trust status, risk score, and safety
|
|
6
|
+
recommendation. Use when agent needs to verify skill safety, or user says
|
|
7
|
+
"is this safe", "check skill", "scan skill", "verify tool", "pyx scan".
|
|
8
|
+
allowed-tools: WebFetch, Bash(curl *)
|
|
9
|
+
argument-hint: "[owner/name]"
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
# PYX Scan — Agent Skill Safety Check
|
|
13
|
+
|
|
14
|
+
Verify whether an AI agent skill is safe before installing or using it by querying the PYX Scanner API.
|
|
15
|
+
|
|
16
|
+
## Workflow
|
|
17
|
+
|
|
18
|
+
### Step 1: Parse Input
|
|
19
|
+
|
|
20
|
+
Extract `owner` and `name` from `$ARGUMENTS`.
|
|
21
|
+
|
|
22
|
+
- Expected format: `owner/name` (e.g., `anthropic/web-search`)
|
|
23
|
+
- If `$ARGUMENTS` is empty or missing the `/` separator, ask the user:
|
|
24
|
+
*"Which skill do you want to check? Provide it as `owner/name` (e.g., `anthropic/web-search`)."*
|
|
25
|
+
- Trim whitespace. Reject if either part is empty after trimming.
|
|
26
|
+
|
|
27
|
+
### Step 2: Call the PYX Scanner API
|
|
28
|
+
|
|
29
|
+
Fetch the safety data:
|
|
30
|
+
|
|
31
|
+
```
|
|
32
|
+
WebFetch URL: https://scanner.pyxmate.com/api/v1/check/{owner}/{name}
|
|
33
|
+
Prompt: "Return the full JSON response body exactly as-is. Do not summarize."
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
If `WebFetch` fails (tool unavailable, network error), fall back to:
|
|
37
|
+
|
|
38
|
+
```bash
|
|
39
|
+
curl -s "https://scanner.pyxmate.com/api/v1/check/{owner}/{name}"
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
### Step 3: Handle Errors
|
|
43
|
+
|
|
44
|
+
| HTTP Status | Meaning | Action |
|
|
45
|
+
|---|---|---|
|
|
46
|
+
| **200** | Skill found | Proceed to Step 4 |
|
|
47
|
+
| **404** | Skill not in database | Verdict = **UNSCANNED** |
|
|
48
|
+
| **429** | Rate limited | Verdict = **ERROR** — "Rate limited. Try again shortly." |
|
|
49
|
+
| **5xx** | Server error | Verdict = **ERROR** — "PYX Scanner is temporarily unavailable." |
|
|
50
|
+
| Network failure | Cannot reach API | Verdict = **ERROR** — "Could not connect to PYX Scanner." |
|
|
51
|
+
|
|
52
|
+
### Step 4: Determine Verdict
|
|
53
|
+
|
|
54
|
+
Use the JSON response fields to determine the verdict:
|
|
55
|
+
|
|
56
|
+
| Condition | Verdict |
|
|
57
|
+
|---|---|
|
|
58
|
+
| `recommendation == "safe"` AND `is_outdated == false` | **SAFE** |
|
|
59
|
+
| `recommendation == "safe"` AND `is_outdated == true` | **OUTDATED** |
|
|
60
|
+
| `recommendation == "caution"` | **CAUTION** |
|
|
61
|
+
| `recommendation == "danger"` | **FAILED** |
|
|
62
|
+
| `recommendation == "unknown"` | **UNSCANNED** |
|
|
63
|
+
|
|
64
|
+
### Step 5: Output Report
|
|
65
|
+
|
|
66
|
+
Format the report as structured markdown. Omit any section where the data is null or empty.
|
|
67
|
+
|
|
68
|
+
**For SAFE verdict:**
|
|
69
|
+
|
|
70
|
+
```
|
|
71
|
+
## PYX Scan: {owner}/{name}
|
|
72
|
+
|
|
73
|
+
**Verdict: SAFE** — This skill has been scanned and verified safe.
|
|
74
|
+
|
|
75
|
+
**Trust Score:** {trust_score}/10 | **Risk Score:** {risk_score}/10 | **Confidence:** {confidence}%
|
|
76
|
+
**Intent:** {intent} | **Status:** {status}
|
|
77
|
+
|
|
78
|
+
### Summary
|
|
79
|
+
{summary}
|
|
80
|
+
|
|
81
|
+
### About
|
|
82
|
+
**Purpose:** {about.purpose}
|
|
83
|
+
**Capabilities:** {about.capabilities as bullet list}
|
|
84
|
+
**Permissions Required:** {about.permissions_required as bullet list}
|
|
85
|
+
|
|
86
|
+
[View full report]({detail_url}) | [Badge]({badge_url})
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
**For OUTDATED verdict:**
|
|
90
|
+
|
|
91
|
+
```
|
|
92
|
+
## PYX Scan: {owner}/{name}
|
|
93
|
+
|
|
94
|
+
**Verdict: OUTDATED** — Last scan was safe, but the skill has been updated since.
|
|
95
|
+
|
|
96
|
+
The scanned commit (`{scanned_commit}`) no longer matches the latest (`{latest_commit}`).
|
|
97
|
+
The new version has NOT been reviewed. Proceed with caution.
|
|
98
|
+
|
|
99
|
+
**Trust Score:** {trust_score}/10 | **Risk Score:** {risk_score}/10
|
|
100
|
+
**Last Safe Commit:** {last_safe_commit}
|
|
101
|
+
|
|
102
|
+
### Summary
|
|
103
|
+
{summary}
|
|
104
|
+
|
|
105
|
+
[View full report]({detail_url})
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
**For CAUTION verdict:**
|
|
109
|
+
|
|
110
|
+
```
|
|
111
|
+
## PYX Scan: {owner}/{name}
|
|
112
|
+
|
|
113
|
+
**Verdict: CAUTION** — This skill has potential risks that need your attention.
|
|
114
|
+
|
|
115
|
+
**Trust Score:** {trust_score}/10 | **Risk Score:** {risk_score}/10 | **Confidence:** {confidence}%
|
|
116
|
+
**Intent:** {intent} | **Status:** {status}
|
|
117
|
+
|
|
118
|
+
### Summary
|
|
119
|
+
{summary}
|
|
120
|
+
|
|
121
|
+
### About
|
|
122
|
+
**Purpose:** {about.purpose}
|
|
123
|
+
**Permissions Required:** {about.permissions_required as bullet list}
|
|
124
|
+
**Security Notes:** {about.security_notes}
|
|
125
|
+
|
|
126
|
+
**Do you want to proceed despite the caution rating?** Please confirm before installing or using this skill.
|
|
127
|
+
|
|
128
|
+
[View full report]({detail_url})
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
**For FAILED verdict:**
|
|
132
|
+
|
|
133
|
+
```
|
|
134
|
+
## PYX Scan: {owner}/{name}
|
|
135
|
+
|
|
136
|
+
**Verdict: FAILED** — This skill has been flagged as dangerous. Do NOT install or use it.
|
|
137
|
+
|
|
138
|
+
**Trust Score:** {trust_score}/10 | **Risk Score:** {risk_score}/10 | **Confidence:** {confidence}%
|
|
139
|
+
**Intent:** {intent} | **Status:** {status}
|
|
140
|
+
|
|
141
|
+
### Summary
|
|
142
|
+
{summary}
|
|
143
|
+
|
|
144
|
+
### About
|
|
145
|
+
**Security Notes:** {about.security_notes}
|
|
146
|
+
|
|
147
|
+
[View full report]({detail_url})
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
**For UNSCANNED verdict:**
|
|
151
|
+
|
|
152
|
+
```
|
|
153
|
+
## PYX Scan: {owner}/{name}
|
|
154
|
+
|
|
155
|
+
**Verdict: UNSCANNED** — This skill has not been scanned by PYX Scanner.
|
|
156
|
+
|
|
157
|
+
No safety data is available. You should:
|
|
158
|
+
1. Review the skill's source code manually before use
|
|
159
|
+
2. Check the skill's repository for known issues
|
|
160
|
+
3. Request a scan at https://scanner.pyxmate.com
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
**For ERROR verdict:**
|
|
164
|
+
|
|
165
|
+
```
|
|
166
|
+
## PYX Scan: {owner}/{name}
|
|
167
|
+
|
|
168
|
+
**Verdict: ERROR** — {error_message}
|
|
169
|
+
|
|
170
|
+
Safety could not be verified. Treat this skill as unverified until you can confirm its safety.
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
## Behavioral Rules
|
|
174
|
+
|
|
175
|
+
1. **Always call the API** — never skip the check or return a cached/assumed result.
|
|
176
|
+
2. **Never soften a FAILED verdict** — if the scan says danger, report danger. Do not add qualifiers like "but it might be fine."
|
|
177
|
+
3. **Always ask user confirmation on CAUTION** — the user must explicitly agree before proceeding.
|
|
178
|
+
4. **Keep reports concise** — omit null/empty sections rather than showing "N/A."
|
|
179
|
+
5. **No raw JSON** — always format the response as the structured markdown report above.
|
|
180
|
+
|
|
181
|
+
## Self-Scan Awareness
|
|
182
|
+
|
|
183
|
+
When `$ARGUMENTS` is `pyxmate/pyx-scan`, `pyxmate/pyx-scanner`, or refers to this skill itself, still call the API honestly and report whatever comes back. If the result is UNSCANNED, append:
|
|
184
|
+
|
|
185
|
+
> *"Yes, even the security scanner's own skill hasn't been scanned yet. We practice what we preach — treat unscanned skills with caution."*
|