Answer questions about Feynman's own product behavior, runtime, settings, commands, skills, connectors, and package state. Use when a response would claim what Feynman can do or how it is wired.
Installs into .claude/skills of the current project.
Are you the author of Product Self Knowledge?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/neversight-product-self-knowledge-learn-skills-dev)
---
name: product-self-knowledge
description: Answer questions about Feynman's own product behavior, runtime, settings, commands, skills, connectors, and package state. Use when a response would claim what Feynman can do or how it is wired.
---
# Product Self Knowledge
Use this skill before making factual claims about Feynman itself.
Workflow:
1. Read source, package metadata, workbench state, or docs that own the behavior.
2. Distinguish local-only, packaged, pushed, deployed, and live-runtime facts.
3. Verify current command/resource discovery when the question concerns skills, prompts, connectors, models, compute, or settings.
4. Name unsupported or untested capability boundaries plainly.
5. Do not infer behavior from the reference app or stale memory when Feynman source can be checked.
Facts about Feynman should cite repo files, command output, or live workbench state.
