Skip to content
Back to skills

Company Ai Policy

ASecurity

Audit an agent system against Kaleva Retail Group's AI and data-usage policies. Produces a row-per-rule compliance report with verdicts (compliant / violating / "I can't tell") and evidence from the target system's files.

  • 4 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 12, 2026
securityrustrailsdatabasesecurity

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add aibot88/sec_skill_store --skill company-ai-policy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Company Ai Policy?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Company Ai Policy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aibot88-company-ai-policy/badge)](https://www.skillsdirectory.com/skills/aibot88-company-ai-policy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: company-ai-policy
description: Audit an agent system against Kaleva Retail Group's AI and data-usage policies. Produces a row-per-rule compliance report with verdicts (compliant / violating / "I can't tell") and evidence from the target system's files.
---

# Company AI Policy — audit skill

Built by Antti for Kaleva Retail Group from their active policies at
the time of the M4 training. Not a generic bundle — it encodes Kaleva's
specific decisions about what's off-limits.

## How to use

Ask Claude to "apply the company-ai-policy skill to [target system]."
Claude will read every rule in `policies/`, walk the target system's
files, and produce a row-per-rule report at `module-4/policy-report.md`.

## Rule sources

- `policies/data-usage.md` — what data an agent may read, what it may
  write, where outputs may land.
- `policies/security.md` — authentication, secret handling, audit
  trails, transitive trust.
- `policies/ai-use.md` — enterprise-agreement rules, model-tier
  restrictions, human-in-the-loop thresholds.
- `policies/sector-rules.md` — retail-sector specific (GDPR for
  customer data, NIS2 adjacencies, PCI-DSS scope boundary).

## Report shape

For each rule across the four policy files, one row:

| Rule | One-line description | Verdict | Evidence |
|---|---|---|---|
| R-XXX | ... | compliant / violating / I can't tell | Quote from target system or `what evidence needed` |

## The "I can't tell" rule

"I can't tell" is a real verdict, not a hedge. Use it when the rule's
compliance cannot be decided from the target files alone. Always pair
with a `what evidence would resolve this` note. Do not upgrade to
"compliant" without evidence; do not downgrade to "violating" on a
hunch.

## Scope

Target is the full Kaleva-shaped agent system: `memory/`, `sources/`,
`agents/`, root `CLAUDE.md`, `module-N/` folders, any `skills/` folders.
Never read customer data stores, production databases, or the
classification-restricted material from Security's draft policy. If the
target references Restricted data, flag as a dependency not a source.

Files in this skill

  • SKILL.md2 KB
  • source.json744 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.