smiles-to-iupac

Translate SMILES strings into IUPAC names using multiple chemical data sources.

52|11|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/InternScience/ChemClaw --skill smiles-to-iupac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smiles-to-iupac
Source: https://github.com/InternScience/ChemClaw/tree/main/skills/smiles-to-iupac
Command: npx skills add https://github.com/InternScience/ChemClaw --skill smiles-to-iupac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rdkit, requests, stout, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Converts SMILES strings into standardized IUPAC names by coordinating multiple naming sources, reducing manual effort and human error in chemical naming.

Core Features & Use Cases

  • Multi-source naming: PubChem, NCI/CADD, STOUT, and RDKit-InChI are queried to provide accurate IUPAC names or InChI when needed.
  • Intelligent fallbacks: automatically degrades to alternative methods when the primary source is unavailable.
  • Property enrichment: computes basic molecular properties via RDKit when available.
  • Use case: labeling large SMILES libraries with correct IUPAC names for cataloging, reporting, or data integration.

Quick Start

Provide a SMILES string and request its IUPAC name to get an immediate result.

Frequently Asked Questions about smiles-to-iupac

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert SMILES strings to IUPAC names for a chemical library?

You can convert SMILES strings to IUPAC names by querying multiple sources like PubChem and NCI/CADD, with automatic fallbacks to STOUT and RDKit-InChI for robust chemical naming.

What is the best way to automate chemical naming across multiple databases?

Automating chemical naming across databases is done by orchestrating queries to PubChem and NCI/CADD, degrading automatically to local STOUT or RDKit-InChI methods when a primary source is unavailable.

Does this SMILES to IUPAC conversion handle cases where PubChem lookup fails?

Yes, SMILES to IUPAC conversion handles PubChem lookup failures by applying intelligent fallbacks, automatically degrading to alternative methods like STOUT or RDKit-InChI to retrieve the chemical name.

Can I compute molecular properties with RDKit while generating IUPAC names?

Yes, you can compute molecular properties with RDKit during IUPAC name generation, as the process enriches the naming workflow by calculating basic molecular properties when the RDKit library is available.

What are the limitations of using STOUT for SMILES to IUPAC name translation?

The limitation of using STOUT for SMILES to IUPAC translation is that it acts as a fallback source, meaning it is utilized only when primary external sources like PubChem or NCI/CADD are unavailable.