writing-bots
Build Safer Silverback Blockchain Bots
Blockchain event bots require precise triggers, network settings, and safety controls. This skill guides Silverback bot design, project structure, testing, and operation.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "writing-bots" from https://skillstore.io/skills/apeworx-writing-bots.md and its manifest at https://skillstore.io/api/skills/apeworx-writing-bots/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "writing-bots". Monitor token transfer events on a testnet and alert an operations channel.
Expected outcome:
A project plan with an event-log trigger, contract configuration, structured alerts, deduplication, logging, and a testnet verification checklist.
Using "writing-bots". Submit a maintenance transaction when a liquidity metric falls below a threshold.
Expected outcome:
A guarded workflow with metric calculation, dry-run mode, signer checks, transaction limits, circuit-breaker conditions, and operator approval.
Using "writing-bots". Review an existing bot before enabling it on mainnet.
Expected outcome:
A risk review covering contract addresses, network selection, state handling, duplicate events, signer permissions, spending limits, observability, and shutdown procedures.
Security Audit
High RiskMost static findings are false positives caused by Markdown formatting or benign environment variable examples. Confirmed findings cover remote documentation fetches, third-party installation, and bot execution; semantic review also identified irreversible blockchain actions and tolerance of unresolved failures.
Confirmed security concerns (2)
Capability review items (5)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (21)
🌐 Network access (4)
🔑 Env variables (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/apeworx-writing-bots/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/apeworx-writing-bots?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/apeworx-writing-bots?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/apeworx-writing-bots/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/apeworx-writing-bots.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
ApeWorX. (2026). writing-bots security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/apeworx-writing-bots/audits/9BibTeX citation
@techreport{apeworx-apeworx-writing-bots-2026,
author = {ApeWorX},
title = {writing-bots security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/apeworx-writing-bots/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "writing-bots security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "ApeWorX"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/apeworx-writing-bots/audits/9"
identifiers:
- type: other
value: "skillstore:apeworx-writing-bots:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Monitor Contract Events
Design a bot that watches contract logs and sends controlled notifications or backend requests.
Automate Protocol Operations
Plan guarded transaction handlers with signer checks, balance limits, and emergency stops.
Track On-Chain Metrics
Define derived metrics and trigger actions when volume, balances, or other signals cross thresholds.
Try These Prompts
Plan a Silverback bot that watches [network] for [contract event] and sends [notification]. Ask for missing requirements before proposing the project.
Draft a Silverback bot for [testnet] that monitors [contract] and records [metric]. Include project files, logging, limits, and circuit-breaker behavior.
Design a Silverback bot that reacts to [trigger] with [off-chain action] and [transaction]. Separate dry-run, testnet, and signer-enabled modes.
Review this Silverback bot for [network]: [requirements or existing design]. Identify failure modes, state assumptions, spending limits, monitoring, and recovery procedures.
Best Practices
- Confirm network, contracts, triggers, actions, and prohibited scenarios before implementation.
- Test without a signer, then use testnet before considering funded mainnet operation.
- Add explicit limits, idempotency, logs, alerts, and circuit-breaker conditions.
Avoid
- Do not install packages or run generated bots without explicit user confirmation.
- Do not enable a signer before reviewing transaction logic and spending boundaries.
- Do not continue privileged testing while failures or state inconsistencies remain unexplained.