Run any Skill in Manus with one click

eds-add-profile-rule

Stars1

Forks0

UpdatedMay 5, 2026 at 12:42

Add a new rule to an edgesentry-rs safety profile. Use when implementing a new regulation-backed detection rule (PROXIMITY_ALERT, ZONE_ENTRY, etc.).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

edgesentry

edgesentry/edgesentry-rs

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	eds-add-profile-rule
description	Add a new rule to an edgesentry-rs safety profile. Use when implementing a new regulation-backed detection rule (PROXIMITY_ALERT, ZONE_ENTRY, etc.).
license	Apache-2.0
compatibility	Requires Rust stable toolchain
metadata	{"repo":"edgesentry-rs"}

Steps

1. Add the rule to rules.json

Open crates/edgesentry-profile/fixtures/<profile-name>/rules.json and add:

{
  "id": "RULE_NAME",
  "condition": "distance < threshold",
  "params": { "threshold": 5.0 },
  "regulation": "Exact regulation citation §X",
  "severity": "HIGH"
}

2. Add a KB file

Create crates/edgesentry-profile/fixtures/<profile-name>/kb/RULE_NAME.md with the plain-language description used by edgesentry-explain.

3. Verify the profile loads

cargo test -p edgesentry-profile

4. Add an integration test

In crates/eds/tests/cli_integration.rs, add a test that:

runs eds ingest replay + eds evaluate run against a fixture
asserts the new RiskEvent fires at the expected frame
asserts evidence_quality is CERTIFIED

Constraints

id must be SCREAMING_SNAKE_CASE and unique within the profile
regulation appears verbatim in AuditRecords — use the exact clause text
KB filename must match id exactly (case-sensitive)

More from this repository

same repository

eds-deploy

edgesentry/edgesentry-rs

Deploy edgesentry-rs to a new server — TLS, PostgreSQL, S3/MinIO, systemd. Use when setting up a new deployment environment.

2026-05-051

eds-dev-workflow

edgesentry/edgesentry-rs

Build, test, and lint edgesentry-rs before committing. Use before every commit or when verifying the workspace is clean.

2026-05-051

eds-new-crate

edgesentry/edgesentry-rs

Scaffold a new crate in the edgesentry-rs Cargo workspace. Use when adding a new pipeline stage or utility crate.

2026-05-051

eds-ops

edgesentry/edgesentry-rs

Operate edgesentry-rs in production — check health, query metrics, run backups, restore from backup. Use when monitoring or maintaining a deployed instance.

2026-05-051

eds-release

edgesentry/edgesentry-rs

Publish a new edgesentry-rs release to crates.io. Use when cutting a release after all tests pass.

2026-05-051

eds-verify-audit-chain

edgesentry/edgesentry-rs

Verify an edgesentry audit chain using the eds CLI. Use to confirm a chain is intact and a payload matches its AuditRecord.

2026-05-051

name	eds-add-profile-rule
description	Add a new rule to an edgesentry-rs safety profile. Use when implementing a new regulation-backed detection rule (PROXIMITY_ALERT, ZONE_ENTRY, etc.).
license	Apache-2.0
compatibility	Requires Rust stable toolchain
metadata	{"repo":"edgesentry-rs"}

Steps

1. Add the rule to rules.json

Open crates/edgesentry-profile/fixtures/<profile-name>/rules.json and add:

{
  "id": "RULE_NAME",
  "condition": "distance < threshold",
  "params": { "threshold": 5.0 },
  "regulation": "Exact regulation citation §X",
  "severity": "HIGH"
}

2. Add a KB file

Create crates/edgesentry-profile/fixtures/<profile-name>/kb/RULE_NAME.md with the plain-language description used by edgesentry-explain.

3. Verify the profile loads

cargo test -p edgesentry-profile

4. Add an integration test

In crates/eds/tests/cli_integration.rs, add a test that:

runs eds ingest replay + eds evaluate run against a fixture
asserts the new RiskEvent fires at the expected frame
asserts evidence_quality is CERTIFIED

Constraints

id must be SCREAMING_SNAKE_CASE and unique within the profile
regulation appears verbatim in AuditRecords — use the exact clause text
KB filename must match id exactly (case-sensitive)