The Semantic Translation Bridge

v1.1.0

Translates rigid scene triggers into rich 6-element spatial intents for smart home control with manual override and personalized mode roaming.

0· 87·0 current·0 all-time
byMilesXiang@spacesq
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (semantic bridge / avatar roaming) match what the package actually does: translate scene names into textual '6-element' intents, merge local avatar habits, write timeline tracks, and log mandates to a local SQLite DB. No unrelated credentials or binaries are requested.
Instruction Scope
SKILL.md instructs the user to run python skill.py and explains the simulated IPC steps. The instructions and code are interactive and will create/read/write files (avatar_habits.json, house_topology.json, rendered_tracks.json, s2_chronos.db) in the current working directory. The README language is grandiose (claims to 'strip hotel AI agent permissions'), but the implementation only simulates that behavior locally—there is no external network/permission escalation in the code.
Install Mechanism
No install spec; this is instruction + code only. No external downloads, package installs, or archive extraction are performed by the skill.
Credentials
The skill requests no environment variables or credentials. All state is stored in local files under the current working directory; no secrets are requested or used.
Persistence & Privilege
always:false and no autonomous elevation. The skill persists data by creating directories, JSON files, and an SQLite DB in os.getcwd(); this is expected for a simulator but means running it in an important filesystem location could overwrite or add files. It does not modify other skills or system-wide settings.
Assessment
This package is largely a local simulator that creates and reads files in whatever directory you run it from. Before running: 1) review skill.py yourself (it is short and readable); 2) run it in an isolated/empty directory or in a container/VM to avoid accidentally creating or overwriting s2_* files or s2_chronos.db in important locations (S2_ROOT = os.getcwd()); 3) note that the 'roaming' and 'permission stripping' claims are narrative: the code only sets local variables and prints status, it does not contact external services or change real hotel systems; 4) if you plan to integrate this with a real S2 ecosystem or networked agents, perform a security review for network calls or auth handling at that integration boundary; 5) do not run as root/admin unless you understand the implications.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ejg7snqrhd56f6agexeja4d83b3cj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments