Skill Trust Decision
ai-customer-service-automation
The skill declares extensive AI automation capabilities but contains no actual implementation code—the only files are documentation (SKILL.md) and a package.json referencing a non-existent index.js entry point.
Why this conclusion was reached
0/4 dimensions flagged Pass
Declared vs actual capability
Declared resources and inferred behavior are broadly aligned.
Review
Hidden execution and egress
1 lower-risk artifacts were extracted and still need context.
Pass
Attack chain and severe findings
There is no explicit malicious chain in the report.
Review
Dependencies and supply chain hygiene
Dependency information is incomplete, so supply-chain confidence stays limited.
What drove the risk score up
Doc-to-code mismatch - declared but not implemented +25
SKILL.md claims AI automation, sentiment analysis, ticket systems, multi-channel support but no actual code exists
Missing implementation file +10
package.json declares main: 'index.js' but the file does not exist in the package
Marketing material posing as documentation +5
SKILL.md is 80% marketing content (pricing, ROI, testimonials) with no technical implementation details
Most important evidence
Medium Doc Mismatch
Declared functionality has no implementation
SKILL.md claims AI-powered features (sentiment analysis, ticket systems, knowledge base sync, multi-channel support) but no source code, scripts, or entry point exists. The only declared entry 'index.js' referenced in package.json is missing.
SKILL.md:1 Request source code before using. This appears to be a documentation-only stub or marketing material.
Low Doc Mismatch
Marketing content masquerading as technical documentation
SKILL.md contains pricing tables, ROI calculations, customer testimonials, and sales copy. A legitimate skill would include actual code examples, API documentation, or technical implementation details.
SKILL.md:1 Verify the skill contains actual implementation before treating as a functional tool.
Declared capability vs actual capability
Filesystem Pass
Declared NONE
→ Inferred NONE
No code files present Network Pass
Declared NONE
→ Inferred NONE
No code files present Shell Pass
Declared NONE
→ Inferred NONE
No scripts/entry points exist Environment Pass
Declared NONE
→ Inferred NONE
No code files present Skill Invoke Pass
Declared NONE
→ Inferred NONE
No code files present Clipboard Pass
Declared NONE
→ Inferred NONE
No code files present Browser Pass
Declared NONE
→ Inferred NONE
No code files present Database Pass
Declared NONE
→ Inferred NONE
No code files present Suspicious artifacts and egress
Dependencies and supply chain
There are no structured dependency warnings.
File composition
2 files · 107 lines
Markdown 1 files · 93 linesJSON 1 files · 14 lines
Files of concern · 1
SKILL.md Declared functionality has no implementation · Marketing content masquerading as technical documentation · [email protected]
Other files · package.json
Security positives
No malicious code present (no scripts, no executables)
No credential harvesting or exfiltration behavior
No obfuscation techniques detected
No sensitive file access attempts
No network requests to external IPs
No supply chain risks (no dependencies)