Skip to content
OpenSmartRoute
Skillv1.0.0

boundary-policy-classification-by-role

Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation

by vamseeachanta(0) 0 installs
Free
Sign in to install

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

See reviews

About

Imported from vamseeachanta/workspace-hub (.claude/skills/workspace-hub/learned/boundary-policy-classification-by-role/SKILL.md). Install upstream with npx skills add vamseeachanta/workspace-hub --skill boundary-policy-classification-by-role. Copyright stays with the author.

Boundary Policy Classification by Role

When defining durable vs transient artifact boundaries within a multi-layer architecture, classify by role not path. Same directory can contain both types (e.g., reports/ has one-shot audits and durable assessments). Ground classification in concrete examples from each layer, validate consistency with parent architecture, and use adversarial review to test for loose language ('it depends') and implementability gaps.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml
targets:
  - https://api.opensmartroute.ai/api/v1/registry/vamseeachanta-workspace-hub-boundary-policy-classificati-7815a3/manifest   # or paste the manifest below

Manifest

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

vamseeachanta-workspace-hub-boundary-policy-classificati-7815a3.ocm.jsonjson
{
  "ocm": "1",
  "id": "vamseeachanta-workspace-hub-boundary-policy-classificati-7815a3",
  "kind": "skill",
  "name": "boundary-policy-classification-by-role",
  "description": "Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation",
  "publisher": "vamseeachanta",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "architecture",
      "policy-design",
      "classification",
      "artifact-management",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Classify artifacts as durable vs transient by their functional role rather than directory path, using multi-layer architectural validation"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/vamseeachanta/workspace-hub",
      "path": ".claude/skills/workspace-hub/learned/boundary-policy-classification-by-role/SKILL.md",
      "ref": "9f24dfff6047b63d4597d2a4ed359f29d969576e",
      "url": "https://github.com/vamseeachanta/workspace-hub/blob/9f24dfff6047b63d4597d2a4ed359f29d969576e/.claude/skills/workspace-hub/learned/boundary-policy-classification-by-role/SKILL.md",
      "key": "vamseeachanta/workspace-hub/.claude/skills/workspace-hub/learned/boundary-policy-classification-by-role/SKILL.md"
    }
  },
  "instructions": "# Boundary Policy Classification by Role\n\nWhen defining durable vs transient artifact boundaries within a multi-layer architecture, classify by *role* not *path*. Same directory can contain both types (e.g., reports/ has one-shot audits and durable assessments). Ground classification in concrete examples from each layer, validate consistency with parent architecture, and use adversarial review to test for loose language ('it depends') and implementability gaps.",
  "cost": {
    "context_tokens": 116
  }
}

Fetch it by URL: GET /api/v1/registry/vamseeachanta-workspace-hub-boundary-policy-classificati-7815a3/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.