← Back to Skills Marketplace
jcools1977

Tidal Lock

by John DeVere Cooley · GitHub ↗ · v1.0.0
darwinlinuxwin32 ⚠ suspicious
270
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install tidal-lock
Description
Detects unhealthy coupling between components — when two modules, services, or layers have become gravitationally locked, unable to change independently. Lik...
Usage Guidance
This skill conceptually fits architecture analysis, but before installing: 1) Ask the author (or review the full SKILL.md) to list exact runtime actions and the minimal required access (e.g., read-only git, path to repo, whether it will call monitoring APIs) and to declare any required binaries. 2) Never grant broad cloud or production monitoring credentials; provide scoped, read-only tokens (or a copy of the repository) for an initial run. 3) Consider running the skill on a sanitized/replicated repository or non-production environment first. 4) Require the skill to declare any external endpoints it will contact and to limit reading of environment variables to those explicitly needed. 5) If you need stronger assurance, request the author publish the analysis scripts (so you can inspect the exact commands) rather than using an instruction-only skill that may exercise broad filesystem and network access.
Capability Analysis
Type: OpenClaw Skill Name: tidal-lock Version: 1.0.0 The provided skill bundle consists solely of metadata (_meta.json) and a detailed conceptual description (SKILL.md). There is no executable code (e.g., Python, shell scripts) or explicit instructions for the AI agent to perform any actions. The SKILL.md file describes a theoretical analysis methodology for code coupling but does not contain any commands, API calls, or prompt injection attempts that would instruct the agent to execute code, access sensitive data, or perform network operations. It explicitly states 'Zero external dependencies. Zero API calls. Pure structural and historical analysis.', which further indicates a benign intent for the described functionality.
Capability Assessment
Purpose & Capability
The name and description align with the content: the skill is an architecture/coupling analysis that needs to map imports, co-changes, shared state, deploy ordering and failure correlations. That capability reasonably explains many of the analysis steps described. However, the skill declares no required binaries, environment variables, or install steps even though the methodology implies the need for git access, code parsing tools, and access to deployment/monitoring systems.
Instruction Scope
The SKILL.md instructs the agent to 'map explicit dependencies (imports, API calls, DB access)', 'map implicit dependencies (shared configs, env vars, timing)', 'git co-change analysis', and 'map failure correlation'. Those steps can require reading repository files, git history, configuration files, environment variables, CI/CD/deployment metadata, and monitoring/logs. The instructions are high-level and do not constrain what the agent may read or query, which gives the agent broad discretion to access many codebase artifacts and possibly sensitive runtime/configuration data.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk during install. That reduces supply-chain risk. However, because there is no bundled tooling, the agent will rely on the runtime environment's tools (git, shell, language parsers), which are not declared.
Credentials
requires.env and primary credential are empty, yet the methodology explicitly references env vars, DB access, deployment dependencies, and failure correlation (which often require monitoring/observability credentials or cloud credentials). The skill does not justify or request the minimal, scoped credentials (for example: read-only git access, readonly monitoring API keys). This omission makes it unclear what secrets or external services the agent will try to access to perform the analysis.
Persistence & Privilege
always is false and the skill does not request persistent installation or modification of other skills. Model invocation is enabled (the platform default) which is expected for a runtime analysis skill; this by itself is not an elevated privilege. No other persistent privileges are requested.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install tidal-lock
  3. After installation, invoke the skill by name or use /tidal-lock
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release — Coupling health analyzer mapping gravitational bonds between components
Metadata
Slug tidal-lock
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Tidal Lock?

Detects unhealthy coupling between components — when two modules, services, or layers have become gravitationally locked, unable to change independently. Lik... It is an AI Agent Skill for Claude Code / OpenClaw, with 270 downloads so far.

How do I install Tidal Lock?

Run "/install tidal-lock" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Tidal Lock free?

Yes, Tidal Lock is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Tidal Lock support?

Tidal Lock is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin, linux, win32).

Who created Tidal Lock?

It is built and maintained by John DeVere Cooley (@jcools1977); the current version is v1.0.0.

💬 Comments