Security Audit

cellxgene-census

github.com/davila7/claude-code-templates

AI SkillCommit 458b11867eae

TRUSTED

Scanned 11 days ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

cellxgene-census received a trust score of 87/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.

SkillShield's automated analysis identified 3 findings: 0 critical, 0 high, 1 medium, and 2 low severity. Key findings include Network egress to untrusted endpoints, Covert behavior / concealment directives, Unpinned dependency in installation instructions.

The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.

Last analyzed on February 12, 2026 (commit 458b1186). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.

Layer Breakdown

Manifest Analysis

91%

Static Code Analysis

98%

Dependency Graph

100%

LLM Behavioral Safety

100%

Behavioral Risk Signals

Network Access

1 finding

Security Findings3

Severity	Finding	Layer	Location
MEDIUM	Network egress to untrusted endpoints HTTP request to raw IP address Review all outbound network calls. Remove connections to webhook collectors, paste sites, and raw IP addresses. Legitimate API calls should use well-known service domains.	Manifest	cli-tool/components/mcps/devtools/figma-dev-mode.json:4
LOW	Covert behavior / concealment directives Multiple zero-width characters (stealth text) Remove hidden instructions, zero-width characters, and bidirectional overrides. Skill instructions should be fully visible and transparent to users.	Manifest	cli-tool/components/mcps/devtools/jfrog.json:4
LOW	Unpinned dependency in installation instructions The installation instructions recommend installing the `cellxgene-census` package without specifying a version. Installing unpinned dependencies can lead to supply chain risks, as new versions might introduce breaking changes, security vulnerabilities, or unexpected behavior. For reproducibility and security, it is best practice to pin dependencies to specific versions. Pin the dependency to a specific version, e.g., `uv pip install cellxgene-census==X.Y.Z`. If `[experimental]` features are used, pin that as well: `uv pip install cellxgene-census[experimental]==X.Y.Z`.	Static	SKILL.md:30

Scan History

Embed Code

[![SkillShield](https://skillshield.io/api/v1/badge/a6b0bc421f386c2d.svg)](https://skillshield.io/report/a6b0bc421f386c2d)