From issueboss
Orchestrate insights-locator and insights-analyzer to find and distill prior context from .insights/. Use when a topic may have prior research, at the start of brainstorming/spec/plan phases, or when the user says "check insights", "research insights", "look for prior context", or "what do we know about X".
npx claudepluginhub szinn/issueboss --plugin issuebossThis skill uses the workspace's default tool permissions.
You are using the `insights-research` skill to surface prior context from `.insights/`.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
You are using the insights-research skill to surface prior context from .insights/.
This skill applies when:
Get topic — use the argument provided, or ask: "What topic should I research in .insights/?"
Dispatch insights-locator via the Agent tool — prompt: Find documents in .insights/ related to: <topic> (include issue slug if known). Wait for result.
Auto-select top 5 from the locator's ranked list. Note the total count for the analyzer. Pass all found documents (up to 5) — if fewer than 5 were found, pass all of them. If the locator returns zero documents, skip steps 4–5 and return:
No prior context found for
<topic>in.insights/.
Dispatch insights-analyzer via the Agent tool — prompt includes the 5 file paths and total found count. Wait for result.
Return findings — present the synthesized findings inline to the user or calling skill.