Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
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 issuebossHow this skill is triggered — by the user, by Claude, or both
Slash command
/issueboss:insights-researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are using the `insights-research` skill to surface prior context from `.insights/`.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
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.