Skill: Reagent Substitute Scout (ID: 108)

When to Use

• - Use this skill when the task needs Find validated alternative reagents based on literature citation data.
• Use this skill for evidence insight tasks that require explicit assumptions, bounded scope, and a reproducible output format.
• Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.

Key Features

See ## Features above for related details.

• - Scope-focused workflow aligned to: Find validated alternative reagents based on literature citation data.
• Packaged executable path(s): scripts/main.py.
• Reference material available in references/ for task-specific guidance.
• Structured execution path designed to keep outputs consistent and reviewable.

Dependencies

• - Python >= 3.8
• requests >= 2.25.0
• pandas >= 1.3.0
• rdkit >= 2021.03.1 (chemical structure analysis)
• biopython >= 1.79 (NCBI API)

Example Usage

See ## Usage above for related details.

CODEBLOCK0

Example run plan:

1. 1. Confirm the user input, output path, and any required config values.
2. Edit the in-file CONFIG block or documented parameters if the script uses fixed settings.
3. Run python scripts/main.py with the validated inputs.
4. Review the generated output and return the final artifact with any assumptions called out.

Implementation Details

See ## Workflow above for related details.

• - Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
• Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
• Primary implementation surface: scripts/main.py.
• Reference guidance: references/ contains supporting rules, prompts, or checklists.
• Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
• Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.

Quick Check

Use this command to verify that the packaged script entry point can be parsed before deeper execution.

CODEBLOCK1

Audit-Ready Commands

Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.

CODEBLOCK2

Workflow

1. 1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
2. Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
3. Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
4. Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
5. If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.

Description

When specific reagents are discontinued or out of stock, find validated alternatives based on literature citation data.

This Skill analyzes reagent usage data from scientific literature to identify alternative reagents that have been repeatedly validated and widely cited, helping researchers quickly find reliable alternatives when the original reagent is unavailable.

Features

• - 🔍 Reagent Identification: Parse reagent names, CAS numbers, molecular formulas, and other multi-dimensional information
• 📚 Literature Analysis: Based on citation data from PubMed, Google Scholar, and other databases
• ✅ Validation Scoring: Calculate usage frequency, success rate, and reliability scores for alternatives
• 🔄 Similarity Matching: Find similar reagents based on chemical structure and functional characteristics
• 📊 Report Generation: Output structured alternative solution reports

Usage

Basic Usage

CODEBLOCK3

Advanced Options

CODEBLOCK4

Configuration

Configuration file path: INLINECODE9

CODEBLOCK5

Output Format

Table Format (Default)

CODEBLOCK6

JSON Format

CODEBLOCK7

Data Sources

1. 1. PubMed/NCBI - Biomedical literature database
2. Google Scholar - Academic citation data
3. ChEMBL - Bioactivity data
4. PubChem - Chemical structure information
5. Local Cache - Historical query results and offline data

Scoring Algorithm

Alternative scoring is based on the following dimensions:

CODEBLOCK8

Installation

CODEBLOCK9

Limitations

• - Literature data completeness depends on database API availability
• Chemical structure similarity calculation requires RDKit support
• Some specialized reagents may lack sufficient public literature data
• It is recommended to combine with actual laboratory conditions to verify alternatives

Version History

• - v1.0.0 (2025-02-06) - Initial version, supports basic query and scoring functions

Author

OpenClaw Skill Development

License

MIT

Risk Assessment

Security Checklist

• - [ ] No hardcoded credentials or API keys
• [ ] No unauthorized file system access (../)
• [ ] Output does not expose sensitive information
• [ ] Prompt injection protections in place
• [ ] API requests use HTTPS only
• [ ] Input validated against allowed patterns
• [ ] API timeout and retry mechanisms implemented
• [ ] Output directory restricted to workspace
• [ ] Script execution in sandboxed environment
• [ ] Error messages sanitized (no internal paths exposed)
• [ ] Dependencies audited
• [ ] No exposure of internal service architecture

Prerequisites

CODEBLOCK10

Evaluation Criteria

Success Metrics

• - [ ] Successfully executes main functionality
• [ ] Output meets quality standards
• [ ] Handles edge cases gracefully
• [ ] Performance is acceptable

Test Cases

1. 1. Basic Functionality: Standard input → Expected output
2. Edge Case: Invalid input → Graceful error handling
3. Performance: Large dataset → Acceptable processing time

Lifecycle Status

• - Current Stage: Draft
• Next Review Date: 2026-03-06
• Known Issues: None
• Planned Improvements:

Output Requirements

Every final response should make these items explicit when they are relevant:

• - Objective or requested deliverable
• Inputs used and assumptions introduced
• Workflow or decision path
• Core result, recommendation, or artifact
• Constraints, risks, caveats, or validation needs
• Unresolved items and next-step checks

Error Handling

• - If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
• If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
• If scripts/main.py fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
• Do not fabricate files, citations, data, search results, or execution outcomes.

Input Validation

This skill accepts requests that match the documented purpose of reagent-substitute-scout and include enough context to complete the workflow safely.

Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:

INLINECODE12 only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.

References

• - references/audit-reference.md - Supported scope, audit commands, and fallback boundaries

Response Template

Use the following fixed structure for non-trivial requests:

1. 1. Objective
2. Inputs Received
3. Assumptions
4. Workflow
5. Deliverable
6. Risks and Limits
7. Next Checks

If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.