skills.rest
AlexKapadia
AlexKapadiaCOMMUNITY
Explore all skills by this author →
GitHub

share-tool

Package a Pixie tool's source code folder into a zip, excluding sensitive files.

6|1|Updated May 17, 2026
Search Tags:#security#package#zip#tool-sharing#secrets-exclusion#tool-transfer#import-tool
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill share-tool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: share-tool
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/share-tool
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill share-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Packages a Pixie tool's SOURCE CODE folder into a zip for sharing, excluding sensitive files like .venv, data/, and .env to prevent leakage.

Core Features & Use Cases

  • Packages a tools/<tool_id>/ folder into a single zip for transfer.
  • Automatically excludes secrets and large cache directories to ensure safe sharing.
  • Use case: share a tool with a teammate or move a tool to another repository via import-tool workflow.

Quick Start

Package the specified tool folder into a zip using the share-tool skill, ensuring secrets are excluded.

Frequently Asked Questions about share-tool

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

FAQPage Schema
How do I package a Pixie tool source code folder into a zip for sharing?▼

To package a Pixie tool for sharing, compress the tools/<tool_id>/ folder into a zip file. This automatically excludes sensitive files like .venv, data/, and .env to prevent secret leakage during transfer.

What's the best way to exclude secrets and .env files when transferring a tool to another repository?▼

The best way to exclude secrets during a tool transfer is to package the tool folder using an automated exclusion process. This filters out .env files, .venv directories, and data/ folders before creating the final zip archive.

Can I duplicate a Pixie tool locally for experimentation without leaking sensitive data?▼

Yes, you can duplicate a Pixie tool locally for experimentation by packaging the source code folder into a zip. This process safely excludes sensitive files like .venv, data/, and .env to prevent accidental leakage.

Does the import-tool workflow require a specific folder structure to transfer tools?▼

Yes, the import-tool workflow requires a preserved tool folder structure. Packaging the tools/<tool_id>/ directory into a zip aligns with this workflow, ensuring the structure remains intact for successful import.

What files are automatically excluded when zipping a tool folder for secure sharing?▼

When zipping a tool folder for secure sharing, sensitive files and large cache directories are automatically excluded. This specifically targets .venv, data/, and .env files to prevent secrets from leaking during transfers.

Related Skills

Explore More Software Engineering Skills→
AlexKapadiaAlexKapadia
6

import-tool

Install a Pixie tool from a ZIP by unpacking under tools/ and validating with uv sync.

Community
Intermediate
012e012e
1

tools

Register frontend and backend tools with UI renderers for LLM assistants.

Community
Advanced
armanzeroeightarmanzeroeight
29

secrets-detector

Detect hardcoded secrets and API keys in source code repositories.

Community
Intermediate
DisbleDisble

no-duplication

Eliminate duplicated test code in Go test files and manage testdata exclusions.

Community
Intermediate