tizen-compliance-checker
Validates Tizen app compliance with TCT (Tizen Compliance Tests). Checks conformance to IoT, TV, or mobile profiles.
Best use case
tizen-compliance-checker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validates Tizen app compliance with TCT (Tizen Compliance Tests). Checks conformance to IoT, TV, or mobile profiles.
Teams using tizen-compliance-checker should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tizen-compliance-checker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tizen-compliance-checker Compares
| Feature / Agent | tizen-compliance-checker | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validates Tizen app compliance with TCT (Tizen Compliance Tests). Checks conformance to IoT, TV, or mobile profiles.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Tizen Compliance Checker Skill **Trit**: -1 (MINUS) **Category**: tizen-security **Author**: Tizen Community **Source**: tizen/security **License**: Apache-2.0 ## Description Validates Tizen app compliance with TCT (Tizen Compliance Tests). Checks conformance to IoT, TV, or mobile profiles. ## When to Use This is a Tizen security/IoT skill. Use when: - Developing Tizen applications (web, native, .NET) - Auditing Tizen app security - Provisioning TizenRT/ARTIK IoT devices - Implementing Tizen compliance - Analyzing SMACK policies or Cynara access control ## Tizen Security Model ### SMACK (Simplified Mandatory Access Control Kernel) - Linux kernel 3.12+ mandatory access control - Process isolation via labels - Prevent inter-app resource access ### Cynara - Fast privilege access control service - Policy-based permission checking - External agent integration ### KeyManager - Central secure storage repository - Password-protected data access - Certificate and key management ### Tizen Manifest - Privilege declarations (public, partner, platform) - App sandboxing configuration - Resource access specifications ## Related Skills - manifest-privilege-validator - smack-policy-auditor - tizen-cve-scanner - sandbox-escape-detector - cynara-policy-checker - iot-device-provisioning ## References - Tizen Official Docs: https://docs.tizen.org/ - Samsung Security Manager: https://github.com/Samsung/security-manager - Samsung Cynara: https://github.com/Samsung/cynara - TizenRT: https://github.com/Samsung/TizenRT
Related Skills
ward-identity-checker
Ward Identity Checker
type-checker
Type Checker Skill
tizen-security-compliance
Maps security requirements to implementation. Coordinates compliance against FIPS 140-3, OCF, CommonCriteria, and Tizen specification.
tizen-cve-scanner
Scans for known Tizen CVEs in app dependencies and kernel. Checks OpenCVE database and Samsung security updates.
tizen-certification-coordinator
Orchestrates Tizen certification workflow. Coordinates TCT test execution, compliance verification, and certification documentation.
tizen-app-scaffold
Generates secure Tizen app projects (native/web/.NET) with privilege declarations, SMACK labels, and secure storage templates pre-configured.
spec-to-code-compliance
Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.
mcp-spec-checker
Predicate-level semantic diff for MCP protocol specs. Compares 0618 vs 1125 specs via Narya types, GF(3) evaluators, and Unison-style effects. Use for protocol verification, spec migration, or detecting breaking changes.
implementing-pci-dss-compliance-controls
PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements
implementing-nerc-cip-compliance-controls
This skill covers implementing North American Electric Reliability Corporation Critical Infrastructure Protection (NERC CIP) compliance controls for Bulk Electric System (BES) cyber systems. It addresses asset categorization (CIP-002), electronic security perimeters (CIP-005), system security management (CIP-007), configuration management (CIP-010), supply chain risk management (CIP-013), and the 2025 updates including mandatory MFA for remote access and expanded low-impact asset requirements.
implementing-aws-security-hub-compliance
Implementing AWS Security Hub to aggregate security findings across AWS accounts, enable compliance standards like CIS AWS Foundations and PCI DSS, configure automated remediation with EventBridge and Lambda, and create custom security insights for organizational risk management.
implementing-aws-config-rules-for-compliance
Implementing AWS Config rules for continuous compliance monitoring of AWS resources, deploying managed and custom rules aligned to CIS and PCI DSS frameworks, configuring automatic remediation with SSM Automation, and aggregating compliance data across accounts.