add-detector

Scaffold detection modules with signal naming and registration patterns.

4|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/highflame-ai/ai-factory --skill add-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-detector
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/add-detector
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill add-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction and inconsistency of adding new detection or analysis modules to extensible services by providing a standardized, spec-driven workflow that ensures telemetry, configuration, and registration are handled correctly.

Core Features & Use Cases

  • Standardized Scaffolding: Automates the creation of module code, registry registration, and configuration wiring.
  • Telemetry Contract Enforcement: Ensures new signals follow the platform's naming conventions for flags, scores, and labels, preventing data loss in observability pipelines.
  • Use Case: When adding a new phishing detection module, this skill guides you through finding the precedent module, implementing the interface, registering the module, and verifying signal emission in the observability store.

Quick Start

Use the add-detector skill to scaffold a new detection module named phishing_detector for the content-analysis service.

Frequently Asked Questions about add-detector

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

FAQPage Schema
How do I scaffold a new detection module for an extensible service?

To scaffold detection modules, you enforce standardized signal naming conventions and registration patterns, ensuring telemetry, configuration, and module registry integration are automatically wired into the service architecture.

What is telemetry contract enforcement for plugin-style services?

Telemetry contract enforcement ensures new signals follow platform naming conventions for flags, scores, and labels, preventing data loss in observability pipelines when adding analysis modules to extensible architectures.

How do I add a phishing detection module to a content-analysis service?

Adding a phishing detection module involves finding a precedent module, implementing the required interface, registering the module in the tier-based registry, and verifying signal emission in the observability store.

Does this scaffolding approach work for centralized configuration management?

Yes, this scaffolding approach satisfies requirements for centralized configuration management by automating the wiring and integration of new detection modules within the service architecture.

Why does my new analysis module fail to emit signals to the observability store?

Analysis modules fail to emit signals when telemetry contracts are not followed, making automated signal extraction fail due to inconsistent naming conventions for flags, scores, and labels.

What's the best way to standardize registration patterns for detection modules?

The best way to standardize registration patterns is using a spec-driven workflow that automates tier-based module registration and configuration wiring for consistent service extension.