add-toolr

Register local files into the seedr registry with type detection and metadata prompts.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/twiced-technology-gmbh/seedr --skill add-toolr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-toolr
Source: https://github.com/twiced-technology-gmbh/seedr/tree/main/.claude/skills/add-toolr
Command: npx skills add https://github.com/twiced-technology-gmbh/seedr --skill add-toolr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of adding new capabilities like skills, hooks, agents, and more to the seedr registry, simplifying content management for developers.

Core Features & Use Cases

  • Automated Content Registration: Adds local files or directories to the seedr registry.
  • Type Detection: Intelligently infers the content type (skill, hook, agent, etc.) from the provided path.
  • Metadata Collection: Gathers necessary information like name, description, and compatibility through interactive prompts.
  • Use Case: You've developed a new custom hook for Claude. Use this Skill to easily register it in your seedr registry, complete with a description and compatibility settings, ready for distribution.

Quick Start

Use the add-toolr skill to register the local hook located at '/Users/daniel/my-hooks/pre-commit-lint'.

Frequently Asked Questions about add-toolr

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

FAQPage Schema
How do I register local content into a custom registry?

To register local content into a custom registry, you parse local filesystem paths and use interactive prompts to collect metadata like name and description, compiling manifest files for accurate cataloging and discoverability.

What is the process for adding custom hooks and agents to a content registry?

Adding custom hooks and agents to a content registry involves detecting content types from provided paths, validating file existence, and inferring slugs to ensure accurate cataloging before generating registry entries.

Can I use automated type detection to register MCP servers and plugins?

Yes, automated type detection intelligently infers whether local content is an MCP server, plugin, skill, or agent from the provided path, streamlining the registration process without manual classification.

How do I catalog local filesystem content for developer tool distribution?

You catalog local filesystem content for developer tool distribution by validating content existence, collecting compatibility settings through interactive prompts, and compiling manifest files for new registry entries.

What are the limitations of inferring slugs during registry registration?

Inferring slugs during registry registration requires valid local filesystem paths and existing content; it cannot generate manifest files for missing directories and relies on interactive prompts to complete metadata collection.