opentide-detection-rule

Name: opentide-detection-rule
Author: opentidehq

Author rules as rule::1.0 YAML under objects/rules/.

by opentidehq(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from opentidehq/opentide (src/opentide/data/setup/skills/authoring/opentide-detection-rule/SKILL.md). Install upstream with npx skills add opentidehq/opentide --skill opentide-detection-rule. Copyright stays with the author.

Detection rules

Author rules as rule::1.0 YAML under objects/rules/.

Shape

metadata.uuid is required. metadata.schema is rule::1.0.
detection_model is the UUID of an objective in objects/objectives/.
Platform query text lives under configurations.<platform>, not a legacy Schemas/ or Configurations/systems path.
Generate a starting file with opentide generate and edit the template it writes.

Check

opentide validate --strict
opentide lint --strict
opentide validate query --platform <platform>
opentide deploy --dry-run

validate checks schema, UUID, and references. lint checks filenames and recommended metadata. Query validation is offline syntax for the platforms that support it.

Installed into a catalogue, chosen by a router

Install opentide-detection-rule and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

opentidehq-opentide-opentide-detection-rule.ocm.jsonjson

{
  "ocm": "1",
  "id": "opentidehq-opentide-opentide-detection-rule",
  "kind": "skill",
  "name": "opentide-detection-rule",
  "description": "Author rules as `rule::1.0` YAML under `objects/rules/`.",
  "publisher": "opentidehq",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "data_analysis"
    ],
    "tags": [
      "skill-md",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Author rules as `rule::1.0` YAML under `objects/rules/`."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/opentidehq/opentide",
      "path": "src/opentide/data/setup/skills/authoring/opentide-detection-rule/SKILL.md",
      "ref": "9047a4e517604bacee4bf2756caf9739a5547e14",
      "url": "https://github.com/opentidehq/opentide/blob/9047a4e517604bacee4bf2756caf9739a5547e14/src/opentide/data/setup/skills/authoring/opentide-detection-rule/SKILL.md",
      "key": "opentidehq/opentide/src/opentide/data/setup/skills/authoring/opentide-detection-rule/SKILL.md"
    }
  },
  "instructions": "# Detection rules\n\nAuthor rules as `rule::1.0` YAML under `objects/rules/`.\n\n## Shape\n\n- `metadata.uuid` is required. `metadata.schema` is `rule::1.0`.\n- `detection_model` is the UUID of an objective in `objects/objectives/`.\n- Platform query text lives under `configurations.<platform>`, not a legacy `Schemas/` or `Configurations/systems` path.\n- Generate a starting file with `opentide generate` and edit the template it writes.\n\n## Check\n\n```bash\nopentide validate --strict\nopentide lint --strict\nopentide validate query --platform <platform>\nopentide deploy --dry-run\n```\n\n`validate` checks sche",
  "cost": {
    "context_tokens": 186
  }
}

Fetch it by URL: GET /api/v1/registry/opentidehq-opentide-opentide-detection-rule/manifest?version=1.0.0