Fix formatting of description in SKILL.md

[cloudbypriyank]

Summary

Fixes the invalid YAML frontmatter in
agent_scan/prompt/skills/agentic-supply-chain-detection/SKILL.md.

The description field contained an unquoted colon, causing YAML
parsing to fail.

Changes

• Quote the description value in the YAML frontmatter.
• No other behavior or skill content was changed.

Related Issue

Closes #577

[boy-hack]

Thanks @cloudbypriyank for the fix! Quoting the description value is the correct fix for the YAML parse error (Closes #577).

One heads-up: this is a duplicate of PR #578 by @NY1024 — both change the exact same line in agent-scan/agent_scan/prompt/skills/agentic-supply-chain-detection/SKILL.md to the same quoted value. To avoid two PRs competing over the same file, could you two coordinate and keep a single one? Either is functionally correct; NY1024's PR also includes the root-cause analysis in its description, but whichever you prefer is fine. Once one is merged, the other should be closed. Thanks!

[NY1024]

Thanks @boy-hack for flagging the duplication! Coordinated with @cloudbypriyank — I've closed my PR #578 so this one (#580) is the single fix going forward.

For reviewer context, here's the root-cause analysis from #578 in case it helps the merge review:

Root cause: The description field in agent-scan/agent_scan/prompt/skills/agentic-supply-chain-detection/SKILL.md contained a bare colon:

description: Detect agentic supply-chain risks: compromised dependencies, malicious plugins/tools/models, and untrusted update sources.

YAML parsers interpret the second colon (risks:) as a nested mapping indicator, triggering mapping values are not allowed in this context at line 2 column 47.

Fix: Quoting the value (as done here in #580) resolves it.

Verification: All 15 SKILL.md files under agent-scan/agent_scan/prompt/skills/ pass yaml.safe_load after the fix.

LGTM — ready to merge. Closes #577.

[boy-hack]

Thanks for the follow-up, @NY1024 — confirming #578 is closed and #580 is the single fix going forward is exactly the coordination we wanted. The root-cause write-up (bare colon in description → YAML mapping values are not allowed) and the yaml.safe_load verification across all 15 SKILL.md files is clean.

This is a correct, minimal one-line fix (quoting the description value). LGTM — ready to merge. Closes #577.