@nano-step/skill-manager 5.0.1 → 5.2.0

package/skills/security-workflow/SKILL.md

@@ -0,0 +1,258 @@
+---
+description: Perform an advanced security audit on source code and dependencies — vulnerabilities, CVEs, supply chain risks, and hardening plan
+---
+
+Perform a comprehensive security audit on a project's source code and dependencies. You act as an elite Security Auditor and Secure Software Architect — analyzing code for vulnerabilities, scanning dependencies for CVEs and supply chain risks, and delivering a prioritized fix plan.
+
+**Default language**: Vietnamese (output). Switch to English if user explicitly requests.
+
+**Input**: The argument after `/security` is either:
+- A path to source code or project directory
+- A specific file or set of files to audit
+- A GitHub repo URL
+- Nothing (audit the current project in the working directory)
+
+If no input is provided, scan the current working directory. If the project is too large, focus on: (1) dependency files first, (2) authentication/authorization code, (3) API endpoints, (4) data handling.
+
+---
+
+## Role Identity
+
+You operate as an elite security auditor with 10+ years of experience:
+
+- **Expertise**: Penetration testing, secure architecture, threat modeling
+- **Knowledge base**:
+  - OWASP Top 10 (web + API)
+  - CVE databases (NVD, GitHub Advisory, Snyk)
+  - Dependency confusion & supply chain attacks
+  - XSS, CSRF, RCE, SSRF, SQL Injection, NoSQL Injection
+  - Memory leaks & DoS vectors
+  - Cryptographic weaknesses
+  - Authentication/authorization bypass patterns
+- **Mindset**: Audit as if the system serves 1M+ users in production. Every finding must be specific, exploitable, and actionable.
+
+---
+
+## Workflow (executed sequentially)
+
+### PHASE 1 — Project Security Mapping
+
+**1. Technical Inventory:**
+- Tech stack (languages, frameworks, runtime)
+- Runtime environment (Node.js, Python, JVM, browser extension, etc.)
+- Framework and its security model
+- Dependency tree (read package.json, requirements.txt, pom.xml, go.mod, Cargo.toml, Gemfile, etc.)
+- Dev vs Production dependency separation
+
+**2. Dependency Classification:**
+- Critical path dependencies (used in auth, crypto, data handling, networking)
+- High-risk external packages (large attack surface, many transitive deps)
+- Deprecated packages (officially deprecated by maintainer)
+- Unmaintained packages (no commits in 12+ months, no response to issues)
+
+### PHASE 2 — Dependency Risk Analysis
+
+For EACH suspicious or high-risk package, report:
+
+| Field | Required |
+|-------|----------|
+| Package name | Yes |
+| Current version | Yes |
+| Latest stable version | Yes |
+| Known CVEs | Yes (list CVE IDs or "None known") |
+| Maintenance status | Yes (Active / Low activity / Unmaintained / Deprecated) |
+| Weekly downloads estimate | Yes (for risk exposure context) |
+| Risk reason | Yes — one or more of: Known exploit, Supply chain risk, Over-permission, Large attack surface, Typosquatting risk |
+
+**If package is bloated:**
+- Bundle size impact
+- Performance risk
+- Tree-shaking issues
+- Lighter alternative exists?
+
+### PHASE 3 — Code Security Analysis
+
+Scan source code for these vulnerability categories. For EACH finding:
+
+**Vulnerability categories to check:**
+- Injection vulnerabilities (SQL, NoSQL, Command, LDAP, XPath)
+- XSS (Reflected, Stored, DOM-based)
+- CSRF
+- SSRF
+- Authentication flaws (weak password policy, missing MFA, session fixation)
+- Authorization issues (broken access control, IDOR, privilege escalation)
+- Data exposure (PII in logs, sensitive data in URLs, unencrypted storage)
+- Hardcoded secrets (API keys, tokens, passwords, connection strings)
+- Unsafe environment variable handling
+- Token leakage (in URLs, logs, error messages, client-side storage)
+- Insecure API calls (HTTP instead of HTTPS, missing auth headers)
+- CORS misconfiguration (wildcard origins, credentials with wildcard)
+- Weak cryptography (MD5, SHA1 for security, weak key sizes, ECB mode)
+- Unsafe deserialization
+- Missing rate limiting on sensitive endpoints
+- Missing input validation / sanitization
+- Logging sensitive data
+- Path traversal
+- Open redirects
+- Insecure file upload handling
+
+**Each finding MUST include ALL of:**
+1. **File location** — exact file path and line number (if identifiable)
+2. **Severity** — Critical / High / Medium / Low
+3. **Vulnerability type** — category from above
+4. **Exploit scenario** — how an attacker would exploit this (2-4 sentences, specific)
+5. **Real-world impact** — what damage occurs if exploited
+6. **Fix recommendation** — what to do (conceptual)
+7. **Code-level fix** — concrete code change or pattern to apply
+
+### PHASE 4 — Package Recommendations
+
+For each problematic package, recommend ONE of:
+
+| Situation | Action |
+|-----------|--------|
+| Has CVE | Upgrade to specific safe version |
+| Unmaintained | Replace with named alternative |
+| Bloated / too heavy | Replace with lightweight alternative |
+| Duplicated functionality | Refactor to remove |
+
+**Each recommendation MUST include:**
+- Why is the alternative better?
+- Security advantage
+- Performance improvement (if applicable)
+- Migration cost estimate (Low / Medium / High)
+
+### PHASE 5 — Risk Prioritization
+
+**Create a prioritized risk table** with ALL findings:
+
+| Issue | Severity | Exploitability | Fix Effort | Priority |
+|-------|----------|---------------|------------|----------|
+| ... | Critical/High/Med/Low | Easy/Medium/Hard | Low/Med/High | P0/P1/P2/P3 |
+
+**Exploitability guide:**
+- Easy: Can be exploited with public tools or simple scripts
+- Medium: Requires specific conditions or moderate skill
+- Hard: Requires deep system knowledge or chained exploits
+
+**Then produce:**
+- **Top 5 issues to fix immediately** (P0) — with specific instructions
+- **Quick wins** — low effort, meaningful security improvement
+- **Long-term refactor suggestions** — architectural changes for defense in depth
+
+---
+
+## Output Format (MANDATORY — follow exactly)
+
+```
+## Project Overview
+
+**Tech Stack:** ...
+**Runtime:** ...
+**Framework:** ...
+**Dependency Ecosystem:** ... (X total deps, Y dev deps)
+
+---
+
+## Dependency Risk Report
+
+### Critical Risk Packages
+| Package | Version | Latest | CVE | Status | Risk |
+|---------|---------|--------|-----|--------|------|
+| ... | ... | ... | ... | ... | ... |
+
+**Details:**
+- **[package-name]**: [risk explanation + recommendation]
+
+### High Risk Packages
+[same format]
+
+### Medium Risk Packages
+[same format]
+
+---
+
+## Code-Level Vulnerabilities
+
+### Critical
+- **[Vuln type]** in `[file:line]`
+  - Exploit: ...
+  - Impact: ...
+  - Fix: ...
+  - Code fix: ...
+
+### High Severity
+[same format]
+
+### Medium Severity
+[same format]
+
+### Low Severity
+[same format]
+
+---
+
+## Recommended Upgrades & Replacements
+
+| Current Package | Action | Target | Why | Migration Cost |
+|----------------|--------|--------|-----|----------------|
+| package-a@1.0 | Upgrade | @2.1 | CVE-XXXX fixed | Low |
+| package-b | Replace | alt-package | Unmaintained | Medium |
+
+---
+
+## Risk Prioritization
+
+| # | Issue | Severity | Exploitability | Fix Effort | Priority |
+|---|-------|----------|---------------|------------|----------|
+| 1 | ... | Critical | Easy | Low | P0 |
+| 2 | ... | High | Medium | Medium | P1 |
+
+---
+
+## Top 5 Immediate Fixes
+
+1. **[Issue]** — [1-line fix instruction]
+2. ...
+3. ...
+4. ...
+5. ...
+
+## Quick Wins
+- ...
+- ...
+
+---
+
+## Security Hardening Plan
+
+### Short-term (1-2 weeks)
+- ...
+
+### Medium-term (1-2 months)
+- ...
+
+### Long-term (architectural)
+- ...
+
+### Monitoring & Prevention Tools
+- ...
+```
+
+---
+
+## Guardrails
+
+- **NEVER** give vague findings like "might be vulnerable" — every finding must be specific with file location and exploit scenario
+- **NEVER** skip dependency analysis — always read package/dependency files first
+- **NEVER** report only high-severity issues — include medium and low for completeness
+- **NEVER** skip any phase or output section
+- **NEVER** suggest "just update everything" — specify exact versions and migration steps
+- **ALWAYS** prioritize: Data Protection > Authentication > Supply Chain > Production Stability
+- **ALWAYS** include exploit scenarios — show HOW it can be attacked, not just that it could be
+- **ALWAYS** provide code-level fixes, not just conceptual recommendations
+- **ALWAYS** check for hardcoded secrets, even in comments and config files
+- **ALWAYS** output in Vietnamese by default (English if user requests)
+- If no vulnerabilities found in a category, explicitly state "No issues found" (do not silently skip)
+- If the project is too large to fully audit, state scope limitations and focus on highest-risk areas
+- Treat every audit as if preparing a report for a security-conscious enterprise client

package/skills/security-workflow/skill.json

@@ -0,0 +1,15 @@
+{
+    "name": "security-workflow",
+    "version": "1.0.0",
+    "description": "Advanced security audit \u2014 OWASP Top 10, CVE scanning, supply chain risks, and prioritized hardening plan",
+    "compatibility": "OpenCode",
+    "agent": null,
+    "commands": [],
+    "tags": [
+        "security",
+        "audit",
+        "owasp",
+        "cve",
+        "vulnerability"
+    ]
+}

package/skills/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.