plugin-author

Guide developers through standardized trading-pipeline plugin creation workflows.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bitandbytes/Argus --skill plugin-author-bitandbytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-author
Source: https://github.com/bitandbytes/Argus/tree/main/.claude/skills/plugin-author
Command: npx skills add https://github.com/bitandbytes/Argus --skill plugin-author-bitandbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers in creating new plugins for the trading pipeline, ensuring consistent interfaces for IndicatorPlugin, SmoothingPlugin, DataEnricher, and SignalFilter, and proper discovery/registration.

Core Features & Use Cases

  • Standardizes the plugin creation process across four core plugin types.
  • Provides a step-by-step workflow: define interfaces, implement plugin, place in the correct module, register in config/plugins.yaml, and write tests.
  • Ensures plugins are discoverable by the registry and validated by tests in CI.

Quick Start

Create a new plugin by implementing its class, placing it in the proper directory, and updating the registry and tests per the guide.

Frequently Asked Questions about plugin-author

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

FAQPage Schema
How do I create a new trading pipeline plugin?

Creating a custom trading pipeline plugin involves implementing the class, placing it in the proper module directory, registering it in config/plugins.yaml, and writing tests to ensure reliable discovery during runtime and backtests.

What are the standard types of trading plugins I can build?

You can build four standard trading plugin types: IndicatorPlugin, SmoothingPlugin, DataEnricher, and SignalFilter, each requiring clear abstractions, parameterization, and stateless design for reliable pipeline integration.

What's the best way to ensure a custom trading indicator is discoverable during backtests?

To ensure a custom trading indicator is discoverable during backtests, you must update the registry in config/plugins.yaml so the system can properly validate the interface conformation and pass CI tests.

Does my SignalFilter plugin need to be stateless?

Yes, your SignalFilter plugin needs to be stateless. The standardized plugin creation workflow requires clear abstractions, parameterization, and stateless design to guarantee reliable discovery during runtime and backtests.

Why does my newly added trading pipeline plugin fail to load at runtime?

Your trading pipeline plugin fails to load at runtime when it lacks interface conformance, is placed in the wrong module directory, or is missing from the config/plugins.yaml registry, thereby preventing proper discovery and validation.