context-verifierKnow the file you're editing is the file you think it is — verify integrity before you act
Install via ClawdBot CLI:
clawdbot install leegitw/context-verifierGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/live-neon/skills/tree/main/agentic/context-verifierAudited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
Developers use the skill to verify file integrity before committing code changes, ensuring they are editing the correct version and detecting any unintended modifications. It prevents conflicts by generating context packets with checksums for peer review workflows, enhancing collaboration and reducing merge errors.
Auditors apply the skill to verify the integrity of financial reports and transaction logs before analysis, using hash verification to confirm files haven't been altered. It supports compliance checks by tagging critical documents and creating verifiable context packets for audit trails.
Healthcare administrators use the skill to ensure patient records and medical files remain unchanged during transfers or updates, verifying integrity with SHA256 hashes. It helps maintain data accuracy by detecting drift and tagging sensitive files as critical for security protocols.
Legal professionals employ the skill to confirm the authenticity of contracts and case files before edits or submissions, using hash computation to prevent tampering. It aids in creating context packets with timestamps and severity tags for evidence tracking in legal proceedings.
Media teams utilize the skill to verify the integrity of video, audio, and design files throughout production pipelines, ensuring assets are unaltered between stages. It enables drift detection and context packet creation for version control, reducing errors in collaborative projects.
Offer the skill as part of a subscription-based platform for developers and enterprises, integrating it with existing DevOps tools for automated integrity checks. Revenue is generated through tiered pricing based on usage volume and advanced features like custom severity tagging.
Provide consulting and customization services to businesses implementing the skill for specific workflows, such as audit trails or compliance verification. Revenue comes from project-based fees for setup, training, and ongoing support tailored to industry needs.
Distribute the skill as open-source under the MIT license, encouraging adoption while offering premium support, enhanced configurations, and priority updates for enterprise clients. Revenue is generated through support contracts and licensing for proprietary extensions.
💬 Integration Tip
Install the skill first in the Neon Agentic Suite to enable foundational integrity checks, and configure it via .openclaw/context-verifier.yaml for seamless integration with other tools.
Scored Apr 19, 2026
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
Persistent memory for AI agents to store facts, learn from actions, recall information, and track entities across sessions.
Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capabi...
Search and discover OpenClaw skills from various sources. Use when: user wants to find available skills, search for specific functionality, or discover new s...
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.