share-skill

Scan skill files for secrets, dangerous patterns, and required registry metadata.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill share-skill-uniquecrete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: share-skill
Source: https://github.com/Uniquecrete/ThinkFasterv1/tree/main/Skills/share-skill
Command: npx skills add https://github.com/Uniquecrete/ThinkFasterv1 --skill share-skill-uniquecrete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fs, path, and includes scripts (resource) components.

What problem does it solve?

It reduces the risk of publishing unsafe or non-compliant skill submissions by validating SKILL.md structure and scanning the skill contents for secrets and dangerous patterns before sharing.

Core Features & Use Cases

  • Safety scan for secrets: Detects likely API keys, tokens, credentials, private keys, and high-entropy secret-like strings.
  • Dangerous-pattern review: Flags potentially risky execution patterns (e.g., eval/exec usage and process/spawn-related patterns) for manual inspection.
  • Registry-ready structure validation: Verifies SKILL.md frontmatter includes required fields and checks that the skill name format matches the folder name.

Quick Start

Run the validator on the target skill directory by executing: validate the skill at the path you want to submit.

Frequently Asked Questions about share-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a skill directory for secrets before submitting it to a registry?

The validator scans skill files to detect API keys, tokens, credentials, private keys, and high-entropy strings before registry submission. It performs deterministic local filesystem scanning using configurable pattern lists to prevent unsafe skill sharing.

What SKILL.md frontmatter fields are required for skill validation?

Skill validation enforces SKILL.md YAML frontmatter requirements and checks that the skill name format matches the folder name. Verifying these required fields ensures your skill is registry-ready and compliant for inclusion in the Zo Skills Registry.

How does dangerous-pattern review work for skill code safety?

Dangerous-pattern review flags potentially risky execution patterns like eval/exec usage and process/spawn-related patterns for manual inspection. This code safety mechanism ensures risky execution logic is identified before sharing skills to the registry.

Can I use this validator for both internal and externally sourced skills?

Yes, you can use this validator for both internal community skills and externally sourced skills. It applies to preparing any skill for inclusion in the Zo Skills Registry by validating structure and scanning for secrets and dangerous patterns.

What are the limitations of local filesystem scanning for skill validation?

Local filesystem scanning limitations include relying on deterministic pattern matching rather than contextual analysis. Dangerous patterns are flagged for manual inspection, meaning the validator cannot autonomously determine the actual safety of complex eval or spawn usage.