← Back to Skills Marketplace
Seismograph
by
John DeVere Cooley
· GitHub ↗
· v1.0.0
275
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install seismograph
Description
Predicts the ripple effects of a proposed change before you make it. Maps how a modification propagates through the codebase — what breaks, what bends, what...
Usage Guidance
Before installing or using this skill, ask the publisher to clarify exactly how it accesses code and downstream systems. Specifically: (1) what files, repo paths, or services does it need to read/write? (2) which binaries or tools must be available (git, language parsers, static analyzers, test runners)? (3) will it ever request or require credentials to external services, and if so, which ones and why? (4) provide concrete runtime steps or a reproducible example run on a small sample repo. Until you get those details, avoid granting repository or service credentials and prefer testing the skill in a disposable sandbox. The current SKILL.md is high-level and ambiguous — that ambiguity increases the risk of unintended data access or exfiltration if the agent is given broad read/network permissions.
Capability Analysis
Type: OpenClaw Skill
Name: seismograph
Version: 1.0.0
The skill bundle describes a detailed code impact analysis tool named 'Seismograph'. The `SKILL.md` outlines a purely analytical process for predicting the ripple effects of code changes, explicitly stating 'Zero external dependencies. Zero API calls. Pure static and historical analysis.' There are no instructions for data exfiltration, malicious execution, persistence, or prompt injection against the agent for harmful purposes. The content is entirely aligned with its stated purpose of code analysis.
Capability Assessment
Purpose & Capability
The skill's purpose is to map propagation across a codebase and downstream systems, which normally requires access to repository files, static-analysis tools, test runners, or service credentials. However, the skill declares no required binaries, environment variables, config paths, or install steps. That absence is disproportionate to the claimed capability and suggests either missing requirements or that the agent will be given broad latitude to 'gather context' at runtime (which is not explicitly described).
Instruction Scope
The SKILL.md describes multi-phase analyses (line-level epicenter mapping, static dependency traversal, dataflow tracing, event/subscriber discovery, downstream monitoring and contract checks) but does not include concrete runtime commands, file paths, or a restricted list of actions. The instructions are high-level and open-ended — they imply reading repository files, running tests, parsing configs, and contacting downstream systems, but do not state how the agent should do these things or what it may access. Open-ended instructions give the agent broad discretion, which is a scope-creep risk.
Install Mechanism
No install spec and no code files are present, which is low risk from an installation-execution perspective. That said, for the described functionality it is surprising there is truly 'zero-dependency' — realistic implementations normally require tools (git, language parsers, static analyzers). The lack of install steps reduces disk/exec risk but increases uncertainty about how the analysis actually happens.
Credentials
The skill declares no required environment variables, credentials, or config paths even though the described analysis would reasonably need access to the repository, CI/test runners, and possibly service credentials for downstream systems. This mismatch could indicate omitted requirements or that the skill expects the agent to request or be granted ad hoc access at runtime — a potential vector for accidental credential exposure or over-broad access.
Persistence & Privilege
The skill does not request 'always' presence and defaults to user-invocable/autonomous invocation as normal. It does not claim to modify other skills or system configuration. No elevated persistent privileges are requested in the provided metadata.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install seismograph - After installation, invoke the skill by name or use
/seismograph - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is Seismograph?
Predicts the ripple effects of a proposed change before you make it. Maps how a modification propagates through the codebase — what breaks, what bends, what... It is an AI Agent Skill for Claude Code / OpenClaw, with 275 downloads so far.
How do I install Seismograph?
Run "/install seismograph" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Seismograph free?
Yes, Seismograph is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Seismograph support?
Seismograph is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin, linux, win32).
Who created Seismograph?
It is built and maintained by John DeVere Cooley (@jcools1977); the current version is v1.0.0.
More Skills