intake

Import external skills and agents with security scans and provenance checks.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/ronniepinnell/casper --skill intake-ronniepinnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/ronniepinnell/casper/tree/main/collection/meta-and-tooling/intake
Command: npx skills add https://github.com/ronniepinnell/casper --skill intake-ronniepinnell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of securely importing external skills and agents into a shared-config environment, ensuring security and provenance while avoiding name collisions and updating the catalog.

Core Features & Use Cases

  • Secure Import: Import skills and agents with security scanning to prevent malicious code.
  • Provenance Stamping: Maintain a record of the origin of each imported skill or agent.
  • Deduplication: Avoid name collisions by checking for existing skills or agents.
  • Catalog Update: Automatically update the catalog with new imported units.
  • Use Case: When you need to integrate third-party skills or agents into your shared-config, use this Skill to ensure a secure and organized import process.

Quick Start

To import a skill from a git URL, use the command: /intake <git-url>

Frequently Asked Questions about intake

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

FAQPage Schema
How do I securely import external agents into a shared-config environment?

To securely import external agents into a shared-config, use a dedicated import process that performs security scans and provenance checks to prevent malicious code. This ensures safe integration of third-party skills.

What is the best way to avoid name collisions when adding third-party skills?

Avoiding name collisions when adding third-party skills requires a deduplication process that checks for existing units before integration. This prevents conflicts and maintains an organized catalog during the import.

How do I track the origin of imported skills and agents?

Tracking the origin of imported skills and agents is done through provenance stamping, which maintains a record of where each unit was acquired. This provides traceability for all external integrations.

Do I need Python to import skills and agents into shared-config?

Yes, you need Python and an appropriate environment setup to execute the secure import process into shared-config. This prerequisite enables the scripts required for security scanning and catalog updates.

How does a security scan work when importing external skills?

A security scan during external skill import works by automatically analyzing the incoming code for malicious patterns before integration. This prevents unsafe dependencies from entering the shared-config catalog.

Can I automatically update my catalog when importing new agents?

Yes, you can automatically update your catalog when importing new agents. The integration process includes a catalog update feature that registers newly imported units after security and deduplication checks pass.