CtrlK
BlogDocsLog inGet started
Tessl Logo

self-awareness

Inspect the active Feynman workbench session, artifacts, execution log, settings, and provenance. Use when the task asks what happened in this session, which files were written, what tools ran, or what remains unverified.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Self Awareness

Use this skill to answer questions about the active Feynman session.

Workflow:

  1. Inspect the workbench state, session logs, execution records, artifact versions, plan files, and settings that own the fact.
  2. Report counts and statuses from current files or API output, not from memory.
  3. Distinguish artifacts produced by chat, notebook, compute, upload, seed fixtures, and manual files.
  4. Identify verification state: checked, inferred, unverified, blocked, or failed.
  5. Keep secrets, private paths, and irrelevant transcript content out of summaries.

This skill is for Feynman introspection, not for querying the local reference app.

Repository
companion-inc/feynman
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.