Install
$ agentstack add skill-byerlikaya-claude-starter-kit-privacy-compliance ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Privacy Compliance (KVKK / GDPR)
Official sources (authority — always defer to these)
The primary, official sources this skill rests on; rules are always interpreted against these:
- KVKK (Turkey): https://www.kvkk.gov.tr/ — the law, regulations, principle decisions, guidelines.
- GDPR (EU): https://gdpr-info.eu/ — article texts (Art.) and Recitals.
If you are unsure about a specific article/threshold/definition (retention period, explicit-consent requirement, the Art. 8 age limit, transfer basis, etc.), check the relevant official source — do not decide from memory or by guessing. In the finding, cite the article you rely on (KVKK Art. … / GDPR Art. …). Fetched content is a reference; you own the interpretation.
Audit axes
- Inventory: what data, collected from where, flowing to where, shared with whom?
- Purpose + basis + retention: for each field, purpose is limited, legal basis is clear, retention period is defined.
- Minimization: data not needed for the purpose is not collected.
- Consent: where required, explicit, recorded, and revocable.
- Transparency: disclosure has been made; the user knows what is collected/processed.
- Data subject rights: access / rectification / erasure / portability / objection are actionable.
- Cross-border transfer & third-party: bound to a legitimate basis (SCC/adequacy/consent).
Output
Per-field/per-flow finding + fix; if "clean", the rationale.
> Project note: If data of minors (children) is processed, special protection is required > (KVKK / GDPR Art. 8 · parental consent & age verification). This is a domain-specific rule and is > defined in the project's own skill/CLAUDE.md — it is not baked into the generic audit. > Project-specific rules (consent texts, retention periods) also live in the project CLAUDE.md.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: byerlikaya
- Source: byerlikaya/claude-starter-kit
- License: MIT
- Homepage: https://www.npmjs.com/package/@byerlikaya/claude-starter-kit
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.