PyOmniTS Usage Guide For Time Series Analysis
PassAudited by ClawScan on May 1, 2026.
Overview
This is a documentation-only PyOmniTS guide, with purpose-aligned advice that may involve cloning third-party code and changing local PyOmniTS files.
This skill appears safe as a usage guide. Before letting an agent follow the replication workflow, confirm which repository it will clone and which PyOmniTS files it will create or overwrite, preferably in a version-controlled checkout.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If followed, the agent may change local PyOmniTS files or scripts, potentially overwriting existing work if names collide.
The guide directs local file-copying and source-file creation or rewriting in a PyOmniTS checkout. This is aligned with adapting code into PyOmniTS, but it affects the user's local project.
Use `cp` to directly copy core folders and files containing model-related codes into `${PYOMNITS_PATH}/layers/${MODEL}.py` ... create an adaptor model class ... Rewrite the loss function to `${PYOMNITS_PATH}/loss_fns/${LOSS}.py`Confirm the target PyOmniTS path, review planned file changes, and use version control or backups before allowing copying or rewriting.
Unreviewed external code could introduce bugs, license issues, or unsafe behavior when later run by the user.
The workflow may import third-party public code into the user's PyOmniTS project. That is expected for model replication, but the artifact does not require pinning a commit or reviewing the source before copying it.
Then, download the code repository you want to adapt (e.g., via `git clone`).
Use trusted repositories, pin a specific commit or release, and inspect code before integrating or executing it.