revalidation

AI Community

Skill notes

Step 1: Structural Validation

Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes: File and directory paths exist and match the documentation. Referenced tools, reference docs, and linked files exist. Named types, classes, dialogs, and namespaces are accurate. Documented conventions still match existing code.

Step 2: Logical Analysis

Analyze the configuration beyond mechanical path checks: Responsibilities align with the available tools and reference files. Conventions still make sense for the current codebase. Sections do not overlap, contradict each other, or duplicate stale guidance. Commonly edited areas are covered.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Structural Validation

Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes: File and directory paths exist and match the documentation. Referenced tools, reference docs, and linked files exist. Named types, classes, dialogs, and namespaces are accurate. Documented conventions still match existing code.

02
Step 2: Logical Analysis

Analyze the configuration beyond mechanical path checks: Responsibilities align with the available tools and reference files. Conventions still make sense for the current codebase. Sections do not overlap, contradict each other, or duplicate stale guidance. Commonly edited areas are covered.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.