skills.rest
PlasticDigits
PlasticDigitsCOMMUNITY
Explore all skills by this author →
GitHub

script-with-timecurve-local

Run local TypeScript or Python scripts against TimeCurve deployments with enforced guardrails.

1|Updated Mar 25, 2026
Search Tags:#typescript#python#guardrails#local-scripts#timecurve#env-hygiene#sale-end-timing
One-click install
npx skills add https://github.com/PlasticDigits/yieldomega --skill script-with-timecurve-local
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: script-with-timecurve-local
Source: https://github.com/PlasticDigits/yieldomega/tree/main/skills/script-with-timecurve-local
Command: npx skills add https://github.com/PlasticDigits/yieldomega --skill script-with-timecurve-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps players and agents author and run local TypeScript or Python scripts against deployed TimeCurve while enforcing environment hygiene, CHARM bounds, cooldowns, and timing near sale end. It clarifies that this is not for patching the main repo and provides guardrails to keep contributor workflows separate.

Core Features & Use Cases

  • Local scripting against TimeCurve deployments using TypeScript or Python.
  • Enforced environment hygiene, CHARM bounds, buy cooldowns, and timing checks to reduce risk.
  • Clear separation between player/agent workflows and repository contributions, with guardrails documented in Phase 18 and related docs.

Quick Start

Run a local TypeScript or Python script against your TimeCurve deployment following the guardrails described in this Skill.

Frequently Asked Questions about script-with-timecurve-local

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

FAQPage Schema
How do I run local scripts against a TimeCurve deployment safely?▼

Run local TypeScript or Python scripts safely against TimeCurve deployments by enforcing environment hygiene, CHARM bounds, and cooldown checks to reduce risk during reads, analysis, or non-patch contributions.

Can I use TypeScript or Python for local TimeCurve scripting?▼

Yes, local TimeCurve scripting supports both TypeScript and Python as runtime choices, allowing players and agents to interact with deployed environments for reads, analysis, and non-patch contributions.

What guardrails are enforced when running local TimeCurve scripts?▼

Guardrails for local TimeCurve scripts include enforced environment hygiene, CHARM bounds, buy cooldowns, and timing checks near sale end to ensure contributor workflows remain separate from repository modifications.

Does local TimeCurve scripting modify the main repository?▼

No, local TimeCurve scripting explicitly does not patch the main repository; it is designed for reads, analysis, and non-patch contributions with enforced separation between player workflows and repository contributions.

Why do I need environment hygiene checks for local TimeCurve scripts?▼

Environment hygiene checks for local TimeCurve scripts reduce risk by enforcing CHARM bounds, buy cooldowns, and sale-end timing constraints, keeping player and agent workflows cleanly separated from main repository contributions.

Related Skills

Explore More Content & Communication Skills→
renderincrenderinc

render-workflows

Scaffold and deploy Render Workflows with Python or TypeScript SDKs.

Official
Advanced
KevinBeanKevinBean

eos-podcast

Generate two-host podcasts from local EmptyOS deployments via localhost:9000.

Community
Advanced
Orda-by-MoveOrda-by-Move

lab-deploy

Automate webnovel deployment by migrating files, syncing Git repositories, and updating project statuses.

Official
Advanced
PlasticDigitsPlasticDigits
1

play-timecurve-doubloon

Explain TimeCurve sale mechanics, DOUB fee routing, and timer settings.

Community
Advanced