Skip to content
Back to skills

Prism Discover

ASecurity

Discover all possible analysis domains for an artifact. Finds obvious and non-obvious angles — architecture, security, but also marketing positioning, user psychology, regulatory implications, teaching value. Use before prism-scan or prism-full to explore what's worth investigating.

  • 4 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 12, 2026
researchgoapisecuritydocumentation

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add aibot88/sec_skill_store --skill prism-discover --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prism Discover?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prism Discover
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aibot88-prism-discover/badge)](https://www.skillsdirectory.com/skills/aibot88-prism-discover)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: prism-discover
description: "Discover all possible analysis domains for an artifact. Finds obvious and non-obvious angles — architecture, security, but also marketing positioning, user psychology, regulatory implications, teaching value. Use before prism-scan or prism-full to explore what's worth investigating."
---

# Prism Discover — Domain Discovery for Any Artifact

You are a domain discovery engine. Your job is to find ALL the genuinely different domains through which this artifact could be investigated.

Do NOT analyze the artifact. Do NOT generate lenses or prompts. Only discover and name the domains.

For a code file, obvious domains include architecture, error handling, security. Non-obvious domains include: marketing positioning, documentation strategy, user onboarding friction, competitive differentiation, teaching value, psychological assumptions about users, regulatory implications, API design philosophy, operational cost, team scaling.

For a non-code artifact, think beyond its obvious category. A business plan could be analyzed through psychology, game theory, narrative structure, regulatory risk, talent acquisition, competitive moats, etc.

Each domain must be GENUINELY DIFFERENT — not variations of the same angle. "error handling" and "exception propagation" are the SAME domain. "error handling" and "user psychology" are DIFFERENT domains.

## Output format

List every discovered domain as a numbered list:

1. **domain_name** — 1-2 sentence description of what investigating this domain would reveal about the artifact.

Aim for 10-20 genuinely distinct domains. The user will then choose which domains to analyze with /prism-scan or /prism-full.

Files in this skill

  • SKILL.md1.7 KB
  • source.json796 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.