Fix Rowan examples for SDK 3.1.13 - #237
Merged
Merged
Conversation
TKassis
approved these changes
Aug 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update the Rowan skill for the current
rowan-python3.1.13 API and bump the skill from v1.4 to v1.5.rowan.Moleculeobjects for workflows that reject bare SMILESMWis exact mass;TopoPSAis topological PSA)ValueError,httpx.HTTPStatusError,rowan.WorkflowError)top_compoundvariableValidation
rowan.whoami()authenticated successfullyMW=180.042,SLogP=1.31,TopoPSA=63.6starlingpKa completed:strongest_acid=9.995rowan.*symbols resolverowancall uses keywords accepted by its 3.1.13 signatureuv run skills-ref validate skills/rowan— passuv run --with pytest python -m pytest tests/_meta -q— 10 passed, 1,213 subtests passedgit diff --check— passThe optional Cisco skill scanner was not run locally because
SKILL_SCANNER_LLM_API_KEYwas not configured; repository PR scanning can cover it.