skills.rest
fianulabs
fianulabsOFFICIAL
Explore all skills by this author →
Website𝕏@fianulabsGitHub

placing-entities-in-hierarchy

Maps framework and category keywords to recommended domains and collections for new controls.

1|Updated Jun 11, 2026
Search Tags:#compliance#collections#nist#soc2#fianu#control placement#domain hierarchy
One-click install
npx skills add https://github.com/fianulabs/fianu-skills --skill placing-entities-in-hierarchy-fianulabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: placing-entities-in-hierarchy
Source: https://github.com/fianulabs/fianu-skills/tree/main/skills/placing-entities-in-hierarchy
Command: npx skills add https://github.com/fianulabs/fianu-skills --skill placing-entities-in-hierarchy-fianulabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When creating a new control or policy on the Fianu compliance platform, agents must decide which domain and collection it belongs to. This Skill removes the guesswork by providing canonical keyword-based mapping tables for consistent placement in the Domain → Collection → Control hierarchy. ## Core Features & Use Cases - Framework-to-Domain Mapping: Recommends domains for NIST 800-53, SOC 2, SOX, GDPR, ISO 27001, and custom internal frameworks. - Keyword-to-Collection Mapping: Maps category keywords (security, QA, access, change, data, observability, infrastructure, governance) to suggested collections. - Cross-Domain Controls: Guides placing a single control into collections across multiple domains without duplicating it. - Use Case: When converting a SOC 2 requirement about access reviews into a control, the Skill recommends the "SOC2 Compliance" domain and the "Access Control" collection, preferring existing collections over new ones. ## Quick Start Ask the agent to decide which domain and collection a new control derived from a NIST 800-53 access control requirement should be placed in.

Frequently Asked Questions about placing-entities-in-hierarchy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which domain a new compliance control belongs to?▼

Map the source framework to a domain using the provided table: NIST 800-53 maps to "NIST Compliance", SOC 2 to "SOC2 Compliance", GDPR to "Data Privacy", and so on. If no matching domain exists, recommend creating one and confirm with a human.

How do I choose a collection for a control based on its category?▼

Extract category keywords from the requirement title or description and match them to collections: security keywords map to "Security", access and identity keywords to "Access Control", and deployment keywords to "Change Management". Prefer existing collections over creating new ones.

Can one control belong to multiple domains or collections?▼

Yes, a single control can belong to collections in two different domains, such as a Code Review control in both Application Compliance and IaC Compliance domains. The control exists once and is referenced from each collection; never duplicate it.

What should I do before recommending placement for a new control?▼

Run the matching-existing-controls skill first to check whether an equivalent control already exists. Only recommend a new control and its placement after confirming no suitable match is present.

What happens if no domain matches the framework of my requirement?▼

If no existing domain matches the framework, the Skill recommends creating a new domain and confirming with a human. Domain sizing guidance suggests 3-6 domains for large enterprises and 1-3 for smaller organizations.

Related Skills

Explore More Legal & Compliance Skills→
open-agreementsopen-agreements
46

soc2-readiness

Map Trust Services Criteria to NIST SP 800-53 controls and identify security gaps.

Official
Advanced
ZeiZelZeiZel
2

research

Conduct multi-source research and generate reports with citations.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

anti-duplication

Search endpoints, components, services, and models for existing implementations before writing code.

Community
Advanced
musher-devmusher-dev

governing-taxonomy

Design documentation taxonomy models with split/nest rules and metadata schemas.

Official
Advanced