You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/skills/curate-aroma-data/SKILL.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,17 +12,19 @@ Build traceable compound tables through the repository's `aromanexus` CLI. Keep
12
12
1. Inspect the input without modifying it.
13
13
- Run `python .agents/skills/curate-aroma-data/scripts/inspect_workbook.py INPUT` from the repository root.
14
14
- Confirm the row count, exact column names, identifier quality, duplicates, and formula-like cells.
15
+
- Identify section labels, headers, totals, and other structural rows before provider calls. Define an explicit dataset-specific skip rule; do not assume that text such as `C6` is globally non-chemical.
15
16
2. Choose the smallest provider set that supplies the requested fields.
16
17
- Read [references/provider-matrix.md](references/provider-matrix.md) before any network or browser operation.
17
18
- Prefer PubChem for canonical identity and sourced odor annotations.
18
19
- Use NIST only for the existing retention-index or name-resolution workflows.
19
20
- Use Pyrfume only for explicitly selected archives after reviewing each manifest note.
20
21
- Use M2OR only when receptor bioassay evidence is relevant; label species and assay scope.
21
22
3. Preview the operation.
22
-
- State the input, new output path, selected provider, expected columns, approximate request count, cache behavior, and material access caveats.
23
+
- State the input, new output path, selected provider, expected columns, skip patterns, approximate request count, cache behavior, and material access caveats.
23
24
- Write a sibling output by default. Do not pass `--force` or overwrite the input unless the user explicitly requests that exact replacement.
@@ -31,6 +33,8 @@ Build traceable compound tables through the repository's `aromanexus` CLI. Keep
31
33
5. Verify the result.
32
34
- Re-run the inspection script on the output.
33
35
- Confirm identical row order and row count, expected new fields, typed status counts, source URL, retrieval time, version, and license/access fields.
36
+
- Treat `PubChem Status` as provider execution state, not proof of a uniquely resolved CAS. Check `PubChem CAS Resolution`, candidate count, and `Resolved CAS` separately.
37
+
- Leave `multiple` and `missing` CAS resolutions unresolved; retain all candidates and route only the affected rows to a targeted fallback source or manual review.
34
38
- Treat `http_error`, `network_error`, `parse_error`, `missing_data`, `data_error`, `partial`, `blocked`, and `skipped` separately from `not_found`.
35
39
- Consult [references/output-schema.md](references/output-schema.md) when reconciling columns or statuses.
36
40
6. Report the output path, provider versions, status counts, partial failures, and any source terms the user must still review.
@@ -43,3 +47,4 @@ Build traceable compound tables through the repository's `aromanexus` CLI. Keep
43
47
- Do not describe the toolkit as AI-powered. Say that structured exports can support downstream statistics, cheminformatics, or machine-learning experiments.
44
48
- Do not bundle or republish downloaded Pyrfume or M2OR data in the repository.
45
49
- Preserve remote text as literal spreadsheet cells to prevent formula execution.
50
+
- Never select the first PubChem CAS candidate merely because the provider status is `ok`.
Every table command writes a sibling file by default, keeps the original row order and columns, and adds provider fields. For example, `compounds.xlsx` becomes `compounds_pubchem.xlsx` after a PubChem run.
114
117
115
-
By default, provenance columns include provider status, source URL, retrieval timestamp, cache hit, pinned version, license URL, and a diagnostic message. Use `--no-provenance` only for legacy-shaped output.
118
+
By default, provenance columns include provider status, source URL, retrieval timestamp, cache hit, pinned version, license URL, and a diagnostic message. PubChem reports CAS resolution separately and populates `Resolved CAS` only when the input is a confirmed CAS or exactly one checksum-valid candidate remains. Multiple or missing candidates stay unresolved. Use `--no-provenance` only for legacy-shaped output.
0 commit comments