Agent Skills › asamassekou10/ship-safe › ship-safe-score

ship-safe-score

GitHub

评估项目安全健康评分（0-100分及A-F等级），分析代码漏洞、依赖风险等类别扣分，并根据评分结果提供修复建议或自动化加固方案。

claude-code-plugin/skills/ship-safe-score/SKILL.md asamassekou10/ship-safe

Trigger Scenarios

用户询问代码是否安全可发布需要快速安全检查项目安全性

Install

npx skills add asamassekou10/ship-safe --skill ship-safe-score -g -y

More Options

Non-standard path

npx skills add https://github.com/asamassekou10/ship-safe/tree/main/claude-code-plugin/skills/ship-safe-score -g -y

Use without installing

npx skills use asamassekou10/ship-safe@ship-safe-score

指定 Agent (Claude Code)

npx skills add asamassekou10/ship-safe --skill ship-safe-score -a claude-code -g -y

安装 repo 全部 skill

npx skills add asamassekou10/ship-safe --all -g -y

预览 repo 内 skill

npx skills add asamassekou10/ship-safe --list

SKILL.md

Frontmatter

{
    "name": "ship-safe-score",
    "description": "Get your project's security health score (0-100, A-F grade). Use when the user wants a quick security check or asks \"is my code safe to ship?\"",
    "argument-hint": "[path] [--no-deps]"
}

Ship Safe — Security Score

You are checking this project's security health score.

Step 1: Run the score command

npx ship-safe@latest score $ARGUMENTS 2>&1

If $ARGUMENTS is empty, default to .:

npx ship-safe@latest score . 2>&1

If the user mentions skipping dependencies, add --no-deps.

The command outputs styled terminal text (not JSON). Parse the output for the score, grade, and category breakdown.

Step 2: Present the results

Extract and present:

Score and Grade: The 0-100 score and A-F letter grade
Category Breakdown: Show deductions per category (Secrets, Code Vulnerabilities, Dependencies)
Grade Meaning:
- A (90-100): Ship it! Your code looks secure.
- B (75-89): Minor issues to review, but generally safe.
- C (60-74): Fix issues before shipping to production.
- D (40-59): Significant security risks present.
- F (0-39): Not safe to ship. Critical issues found.

Step 3: Recommendations

Based on the score:

A or B (75+): Congratulate the user. Suggest running npx ship-safe guard to install a pre-push git hook that maintains the score. Mention they can run /ship-safe for a detailed breakdown anytime.
C (60-74): Recommend running /ship-safe for a full audit to see exactly what needs fixing. Mention the most likely problem areas based on the category breakdown.
D or F (below 60): Strongly recommend running /ship-safe immediately. Offer to start the full audit right now. Emphasize that critical findings should be fixed before any deployment.
For any score, mention /ship-safe-baseline to track progress over time and /ship-safe-fix for automated remediation.