@intentsolutionsio/severity1-marketplace 1.0.0 → 1.0.4

package/agents/severity-triage.md

@@ -1,6 +1,35 @@
 ---
 name: severity-triage
 description: Automated severity triage agent for issues and vulnerabilities
+tools:
+- Read
+- Write
+- Edit
+- Bash
+- Glob
+- Grep
+- WebFetch
+- WebSearch
+- Task
+- TodoWrite
+model: sonnet
+color: blue
+version: 1.0.0
+author: Jeremy Longshore <jeremy@intentsolutions.io>
+tags:
+- security
+- severity
+- triage
+disallowedTools: []
+skills: []
+background: false
+# ── upgrade levers — uncomment + set when tuning this agent ──
+# effort: high            # reasoning depth: low/medium/high/xhigh/max (omit = inherit session)
+# maxTurns: 50            # cap the agentic loop (omit = engine default)
+# memory: project         # persistent scope: user/project/local (omit = ephemeral)
+# isolation: worktree     # run in an isolated git worktree
+# initialPrompt: "…"      # seed the agent's first turn
+# hooks / mcpServers / permissionMode → set at the PLUGIN level, not on a plugin agent
 ---
 # Severity Triage Agent
 

package/commands/severity-classify.md

@@ -10,6 +10,7 @@ Analyze the provided issue, bug report, or security finding and assign an approp
 ## Severity Levels
 
 ### S1 — Critical
+
 - System completely down or unusable
 - Active data loss or corruption
 - Security breach with confirmed exploitation
@@ -17,6 +18,7 @@ Analyze the provided issue, bug report, or security finding and assign an approp
 - **Response time:** Immediate
 
 ### S2 — High
+
 - Major functionality broken for many users
 - Security vulnerability with high exploitability
 - Data integrity at risk
@@ -24,6 +26,7 @@ Analyze the provided issue, bug report, or security finding and assign an approp
 - **Response time:** Within 4 hours
 
 ### S3 — Medium
+
 - Functionality degraded but operational
 - Security issue with limited scope
 - Reasonable workaround available
@@ -31,6 +34,7 @@ Analyze the provided issue, bug report, or security finding and assign an approp
 - **Response time:** Within 24 hours
 
 ### S4 — Low
+
 - Minor issue or cosmetic defect
 - Enhancement request
 - Documentation improvement

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intentsolutionsio/severity1-marketplace",
-  "version": "1.0.0",
+  "version": "1.0.4",
   "description": "Severity level classification and prompt improvement for marketplace plugins. Assigns severity ratings (S1-Critical through S4-Low) and enhances plugin prompts for clarity, safety, and effectiveness.",
   "keywords": [
     "severity",

package/skills/prompt-improver/SKILL.md

@@ -1,13 +1,19 @@
 ---
 name: prompt-improver
-description: |
-  Analyze and improve plugin prompts, skill definitions, and command instructions for clarity, safety, and effectiveness. Use when the user asks to "improve a prompt", "review a skill", "enhance instructions", "make this prompt better", "optimize this command", or "audit prompt quality".
+description: 'Analyze and improve plugin prompts, skill definitions, and command instructions
+  for clarity, safety, and effectiveness. Use when the user asks to "improve a prompt",
+  "review a skill", "enhance instructions", "make this prompt better", "optimize this
+  command", or "audit prompt quality".
+
+  '
 allowed-tools: Read, Write, Edit, Glob, Grep
 version: 1.0.0
 author: severity1 <severity1@intentsolutions.io>
 license: MIT
-tags: [security, compliance]
-compatible-with: claude-code
+tags:
+- security
+- compliance
+compatibility: Designed for Claude Code
 ---
 # Prompt Improver
 
@@ -20,6 +26,7 @@ The prompt-improver skill evaluates plugin content across five dimensions — cl
 ## When to Use This Skill
 
 This skill activates when you need to:
+
 - Review and improve a SKILL.md file's instructions
 - Enhance command or agent markdown definitions
 - Audit prompt quality across a plugin
@@ -76,11 +83,13 @@ This skill activates when you need to:
 ### Example 1: Improving a vague skill description
 
 **Before:**
+
 ```yaml
 description: Does stuff with code
 ```
 
 **After:**
+
 ```yaml
 description: |
   Analyze source code for common anti-patterns and suggest refactoring improvements. Use when the user asks to "review code quality", "find code smells", or "refactor this file".
@@ -89,11 +98,13 @@ description: |
 ### Example 2: Adding missing safety guidance
 
 **Before:**
+
 ```markdown
 Delete all temporary files from the project.
 ```
 
 **After:**
+
 ```markdown
 Identify temporary files (*.tmp, *.bak, *.swp) in the project. List them for user confirmation before deletion. Never delete files outside the project root.
 ```
@@ -107,6 +118,7 @@ Identify temporary files (*.tmp, *.bak, *.swp) in the project. List them for use
 ## Output
 
 The skill produces a structured analysis report containing:
+
 - **Score card**: 5 dimensions rated 1-5 with notes and an overall score out of 25
 - **Improvement list**: Specific weaknesses with file paths and line references
 - **Suggested rewrite**: Full improved prompt text preserving original intent

package/skills/prompt-improver/references/severity-levels.md

@@ -5,6 +5,7 @@
 **Definition:** System-down, active data loss, or confirmed security breach requiring immediate response.
 
 **Indicators:**
+
 - Production system completely unavailable
 - Active data corruption or loss
 - Confirmed security exploitation in progress
@@ -14,6 +15,7 @@
 **Response:** Immediate — all hands on deck
 
 **Examples:**
+
 - SQL injection actively being exploited
 - Database corruption causing data loss
 - Authentication bypass allowing unauthorized access
@@ -24,6 +26,7 @@
 **Definition:** Major functionality broken or security vulnerability with high exploitability requiring urgent resolution.
 
 **Indicators:**
+
 - Core feature non-functional
 - Security vulnerability with known exploit path
 - Data integrity at risk but not actively compromised
@@ -32,6 +35,7 @@
 **Response:** Within 4 hours
 
 **Examples:**
+
 - Payment processing failing for subset of users
 - XSS vulnerability in user input fields
 - API rate limiting completely broken
@@ -42,6 +46,7 @@
 **Definition:** Degraded functionality with reasonable workaround available, scheduled for normal fix cycle.
 
 **Indicators:**
+
 - Feature works but with reduced capability
 - Security issue with limited scope or low exploitability
 - Workaround is available and practical
@@ -50,6 +55,7 @@
 **Response:** Within 24 hours
 
 **Examples:**
+
 - Search results occasionally missing items
 - CSRF token not rotating on session refresh
 - Export feature produces incorrect formatting
@@ -60,6 +66,7 @@
 **Definition:** Minor issue, cosmetic defect, or enhancement request for the backlog.
 
 **Indicators:**
+
 - Cosmetic or UI inconsistency
 - Documentation error
 - Enhancement request
@@ -68,6 +75,7 @@
 **Response:** Backlog prioritization
 
 **Examples:**
+
 - Typo in error message
 - Button color inconsistent with design system
 - Feature request for additional export format