cross-plugin-detective

Map agent roles to detective skills across frontend, bun, and code-analysis plugins.

2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/tianzecn/myclaudecode --skill cross-plugin-detective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-plugin-detective
Source: https://github.com/tianzecn/myclaudecode/tree/main/plugins/code-analysis/skills/cross-plugin-detective
Command: npx skills add https://github.com/tianzecn/myclaudecode --skill cross-plugin-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claudemem, and includes references (resource) components.

What problem does it solve?

This Skill provides integration guidance for mapping agent roles (frontend/bun) to the appropriate detective skills, enabling consistent cross-plugin investigations.

Core Features & Use Cases

  • Agent-to-Skill Mapping: translate agent roles to detective capabilities.
  • Unified Investigation: ensure consistent tooling across plugins.
  • Guided Orchestration: streamline cross-plugin analysis workflows.

Quick Start

Map a frontend-developer to developer-detective or a bun-api-architect to architect-detective and run semantic investigations accordingly.

Frequently Asked Questions about cross-plugin-detective

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

FAQPage Schema
How do I map agent roles to detective skills across multiple plugins?

Cross-plugin detective maps frontend and backend agent roles (developer, architect, tester, debugger, ultrathink) to corresponding detective skills. It uses claudemem-indexed memory to route agents to the correct skill based on role, enabling consistent investigation workflows across plugins without grep or find operations.

What agent roles can be routed to detective skills in this integration?

Five detective roles are supported: developer-detective for finding implementations, architect-detective for architecture analysis, tester-detective for test quality assessment, debugger-detective for comprehensive reviews, and ultrathink-detective for advanced reasoning. Each routes frontend and bun backend agents to their designated skill.

Can I use this skill to trace data flow and architecture across plugins?

Yes. The skill enables architecture analysis and data flow tracing by mapping agent roles to architect-detective, which performs cross-plugin investigation using claudemem indexed memory for semantic searches across frontend, bun backend, and code-analysis plugins.

Why should I use role-based routing instead of manual skill selection?

Role-based routing enforces a fixed decision policy that eliminates manual skill assignment overhead, ensures consistent detective tool usage across plugins, and automates the mapping of agent context to appropriate investigation capabilities for standardized cross-plugin analysis.

Does this skill work with frontend, backend, and code-analysis plugins?

Yes. The skill integrates frontend plugin agents, bun backend plugin agents, and code-analysis plugins. It routes all three agent types to detective skills and forbids grep/find usage, relying instead on claudemem semantic indexing for discovery.

What indexing method does this skill use for cross-plugin searches?

Cross-plugin detective uses claudemem indexed memory for all searches. This enables semantic investigation across plugins while forbidding traditional grep or find commands, ensuring consistent memory-backed discovery instead of file system search patterns.