datasheet diff reader

Data Community

Skill notes

Core Workflow

Gather the full input corpus and normalize messy, repetitive, or partial artifacts into a usable working set. Cluster related items into themes, categories, or issue groups without flattening important differences. Extract the strongest signals, representative examples, and unresolved questions from each cluster. Produce a structured summary that is actionable for the next human or agent in the workflow.

Deliver

A clear thematic summary or grouped output with representative evidence. The most important patterns, edge cases, and unknowns in the corpus. Actionable next steps, owners, or decisions when the task calls for them.

Guardrails

Do not over-merge distinct issues just to simplify the summary. Preserve nuance when a cluster contains disagreement or uncertainty. Make the grouping logic legible enough that someone can audit it later. Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
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
@00PrabalK00 · 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
Network behavior
Local-only
Install commands
None (reference only)

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

Author source file SKILL.md

# Datasheet Diff Reader

## Overview

Compare two part datasheet revisions and flag electrical, timing, package, or lifecycle changes that matter.

## Core Workflow

1. Gather the full input corpus and normalize messy, repetitive, or partial artifacts into a usable working set.
2. Cluster related items into themes, categories, or issue groups without flattening important differences.
3. Extract the strongest signals, representative examples, and unresolved questions from each cluster.
4. Produce a structured summary that is actionable for the next human or agent in the workflow.

## Deliver

- A clear thematic summary or grouped output with representative evidence.
- The most important patterns, edge cases, and unknowns in the corpus.
- Actionable next steps, owners, or decisions when the task calls for them.

## Guardrails

- Do not over-merge distinct issues just to simplify the summary.
- Preserve nuance when a cluster contains disagreement or uncertainty.
- Make the grouping logic legible enough that someone can audit it later.
- Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.

Discussion

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