Security Policy

Security Commitment

Skills IL employs multiple layers of protection to secure skills on the platform. Every skill goes through automated analysis and manual approval before publication.

Review Process

Step 1: Permission Analysis

Each skill declares the tools it needs. The system analyzes these permissions and rates them by risk level. Skills that require broad permissions (such as terminal or filesystem access) receive lower scores, while skills with narrow permissions are rated higher.

Step 2: Risky Pattern Detection

The system scans skill content to identify concerning patterns, including:

Environment variable access
Filesystem operations
Network calls
Dynamic code execution

This detection is content-based and flags patterns that may indicate risky behavior.

Step 3: External Security Scanners

Skill repositories may include security scans from external tools such as Snyk and Cisco. When results are available, we display them on the skill page.

Step 4: Manual Approval

Every new skill requires manual approval before publication. Skills are not visible to the public until approved, and can be rejected with notes.

Step 5: Trust Score

Each skill receives a trust score based on multiple dimensions, including:

Code Quality - community activity around the project
Permissions - level of access the skill requires
Data Handling - presence of sensitive patterns
Publisher Reputation - publishing history
Maintenance - project freshness
Documentation - completeness of documentation and licensing

The score determines the trust tier: Verified, Trusted, Community, or Under Review.

Frontmatter Security

Skill definitions (frontmatter) appear in the agent's system prompt. Therefore:

Content that could be used for prompt injection is rejected by validation
Reserved AI provider names are blocked
Definitions are parsed safely without code execution
Displayed content is sanitized before rendering

Vulnerability Reporting

If you found a security vulnerability, please report it privately through one of the following channels:

Private report on GitHub - preferred, allows private discussion until a fix is released
Email: security@agentskills.co.il

Important: Please do not open a public issue for security vulnerabilities. Private reporting allows us to fix the problem before it is disclosed.

We aim to address every report within 48 hours.

Updates

This policy is regularly updated. Last update: March 2026.

Review Process

Step 1: Permission Analysis

Step 2: Risky Pattern Detection

The system scans skill content to identify concerning patterns, including:

Environment variable access

Filesystem operations

Network calls

Dynamic code execution

This detection is content-based and flags patterns that may indicate risky behavior.

Step 3: External Security Scanners

Skill repositories may include security scans from external tools such as Snyk and Cisco. When results are available, we display them on the skill page.

Step 4: Manual Approval

Every new skill requires manual approval before publication. Skills are not visible to the public until approved, and can be rejected with notes.

Step 5: Trust Score

Each skill receives a trust score based on multiple dimensions, including:

Code Quality - community activity around the project

Permissions - level of access the skill requires

Data Handling - presence of sensitive patterns

Publisher Reputation - publishing history

Maintenance - project freshness

Documentation - completeness of documentation and licensing

The score determines the trust tier: Verified, Trusted, Community, or Under Review.

Vulnerability Reporting

If you found a security vulnerability, please report it privately through one of the following channels:

Important: Please do not open a public issue for security vulnerabilities. Private reporting allows us to fix the problem before it is disclosed.

We aim to address every report within 48 hours.