ee-datasheet-master
Use when user has/is reading a component datasheet or spec sheet to find chip parameters: pinout, voltage, I2C address, timing, register map, electrical characteristics. Trigger on PDF+chip questions. Also: 规格书, 数据手册, 芯片参数. All IC types.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/baorepo/ee-datasheet-masterEE Datasheet Master
Iron Law: PDF Content Only
ALL DATA MUST ORIGINATE FROM THE PDF.
Allowed: Extract → Calculate from extracted data
Forbidden: Use prior knowledge → Fill gaps with guesses
Allowed Derivations
| Type | Example |
|---|---|
| Mathematical calculation | P = V × I from voltage and current |
| Unit conversion | dBm → mW, binary → hex |
| Address calculation | "001000x" → 0x10/0x11 |
| Counting | Pin count from Pin Description table |
When deriving: Show source data (page) + calculation steps + result
Forbidden Behaviors
| Behavior | Correction |
|---|---|
| "I know this chip..." | Find the spec in PDF |
| "Typical value is..." | Read the actual value from PDF |
| "Similar chips have..." | This one may differ |
| Guessing to fill gaps | Output "NOT SPECIFIED IN DATASHEET" + acquisition path (see below) |
When the PDF Cannot Provide the Answer
"NOT SPECIFIED IN DATASHEET" is not a dead end. Always follow it with how to obtain the missing information.
Response Template
"[Parameter] is not specified in this datasheet. To obtain it: [specific method below]."
If the datasheet references an application note or supplementary doc by name, cite it:
"Section X references Application Note [AN-xxx] for this topic — search [Manufacturer] website."
Reasoning Framework for Missing Parameters
When a parameter is absent, reason through these questions to give a concrete, actionable path:
1. Why is it missing?
- Wrong document — this is a brief/product datasheet; the full reference manual or application note contains it → identify the correct document by name
- Test-condition mismatch — the spec exists but not at the user's specific conditions (load, frequency, temperature) → explain which conditions differ and how that affects the value
- Application-dependent — the value depends on external components or PCB layout the user controls → explain what determines it and how to calculate or simulate
- Manufacturer-controlled — the data is from qualification testing, not released publicly → identify the right contact channel
2. What does the user actually need it for?
- Design margin check → an approximation or worst-case bound may be sufficient
- Debugging a failure → direct measurement in the actual circuit is more reliable than a datasheet value
- Qualification / compliance → only manufacturer-provided data is acceptable
3. What is the most direct path given the above? Tailor the recommendation to the specific parameter and context — a thermal resistance question for an LDO in a hot enclosure calls for a different answer than the same question for a signal-path op-amp. Reason about: what equipment would give this measurement, what document would contain this spec, or what formula derives this value from things the user can measure or control.
6-Phase Workflow
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-baorepo-ee-datasheet-master": {
"enabled": true,
"auto_update": true
}
}
}