소스 정보
- 저장소
- tomevault-io/skills-registry
- 최근 소스 활동
- 2026년 5월 11일 15:30
- 감지된 SKILL.md 언어
- 영어
- 스타
- 0
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/tomevault-io/skills-registry --skill trestle-jinja-templating명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | trestle-jinja-templating |
| description | >- Use when this capability is needed. |
Trestle provides a Jinja2-based templating system (trestle author jinja) for generating compliance documents from OSCAL data. Templates can reference SSPs, profiles, and catalogs to produce formatted markdown or other document formats.
trestle author jinja -i <template_path> -o <output_path> [options]
Trestle extends Jinja2 with three custom tags:
Include a specific section from a markdown file by heading title:
{% mdsection_include "path/to/file.md" "Section Title" heading_level=2 %}
heading_level controls which heading level to search for (default: based on document structure)Include an entire markdown file, stripping YAML frontmatter:
{% md_clean_include "path/to/file.md" heading_level=2 %}
--- markers)heading_levelInsert a formatted date stamp:
{% md_datestamp format="%Y-%m-%d" newline=True %}
format follows Python strftime format stringsnewline adds a trailing newline (default: True)| Filter | Description | Example |
|---|---|---|
as_list | Convert value to a list | {{ value | as_list }} |
get_default | Get the default value | {{ param | get_default }} |
first_or_none | Get first element or None | {{ items | first_or_none }} |
get_party | Get party by UUID from SSP | {{ ssp | get_party(uuid) }} |
parties_for_role | Get all parties for a role ID | {{ ssp | parties_for_role(role_id) }} |
diagram_href | Get diagram link href | {{ diagram | diagram_href }} |
When an SSP is provided (--ssp), these objects are available in templates:
| Variable | Type | Description |
|---|---|---|
ssp | SystemSecurityPlan | The full SSP object |
catalog | Catalog | Resolved catalog from the SSP's profile |
catalog_interface | CatalogInterface | Utility for querying catalog controls |
control_interface | ControlInterface | Utility for working with individual controls |
control_writer | DocsControlWriter | Writer for formatting control documentation |
ssp_md_writer | SSPMarkdownWriter | Writer for SSP markdown output |
When --docs-profile is used for per-control output:
| Variable | Type | Description |
|---|---|---|
profile | Profile | The profile being processed |
control | Control | Current control being rendered |
group_title | str | Title of the control's group |
Provide additional variables via a YAML lookup table (-lut):
# lookup.yaml
system_name: My Federal System
authorization_date: 2024-01-15
fips_level: Moderate
# In template
System Name: {{ system_name }}
Authorization Date: {{ authorization_date }}
The -bf / --bracket-format flag controls how parameter values appear:
| Format | Example Output |
|---|---|
[.] | [value] |
((.)) | ((value)) |
| None | value (no brackets) |
Use -vap and -vnap to prefix values based on assignment status:
-vap "Assigned: " — prefix when parameter has a value-vnap "MISSING: " — prefix when parameter has no value---
title: System Security Plan
date: {% md_datestamp format="%B %d, %Y" %}
---
# {{ ssp.system_characteristics.system_name }}
## System Description
{{ ssp.system_characteristics.description }}
## Authorization Boundary
{% mdsection_include "boundary.md" "Authorization Boundary" heading_level=2 %}
## Leveraged Services
{% for leveraged in ssp.system_implementation.leveraged_authorizations %}
- {{ leveraged.title }}
{% endfor %}
# Control: {{ control.id }}
{% for part in control.parts %}
## {{ part.name }}
{{ part.prose }}
{% endfor %}
### Responsible Parties
{% for role in control.responsible_roles %}
- {{ role.role_id }}: {% for party_uuid in role.party_uuids %}{{ ssp | get_party(party_uuid) }}{% endfor %}
{% endfor %}
Assessment data is not directly available as Jinja context objects (unlike SSPs). To use assessment and POA&M data in Jinja templates, pre-extract the data into YAML lookup tables and pass them via -lut.
Prepare a lookup table with extracted assessment data:
# assessment-lookup.yaml
assessment_title: "Annual Security Assessment 2024"
assessment_date: "2024-02-28"
assessor: "Security Assessment Team"
total_controls: 45
satisfied_count: 38
not_satisfied_count: 5
other_count: 2
findings:
- control_id: "AC-1"
title: "Outdated Access Control Policy"
status: "not-satisfied"
risk_level: "High"
observation: "Policy last updated 3 years ago"
- control_id: "AC-2"
title: "Account Management"
status: "satisfied"
risk_level: "N/A"
observation: "Account management procedures verified"
- control_id: "SC-7"
title: "Boundary Protection"
status: "satisfied"
risk_level: "N/A"
observation: "Network boundary controls verified via scan"
Template for an assessment report:
---
title: {{ assessment_title }}
date: {% md_datestamp format="%B %d, %Y" %}
---
# Assessment Report: {{ assessment_title }}
**Assessment Date:** {{ assessment_date }}
**Assessor:** {{ assessor }}
## Summary
| Metric | Count |
|--------|-------|
| Total Controls Assessed | {{ total_controls }} |
| Satisfied | {{ satisfied_count }} |
| Not Satisfied | {{ not_satisfied_count }} |
| Other | {{ other_count }} |
## Findings Summary
| Control | Title | Status | Risk Level |
|---------|-------|--------|------------|
{% for finding in findings -%}
| {{ finding.control_id }} | {{ finding.title }} | {{ finding.status }} | {{ finding.risk_level }} |
{% endfor %}
## Detailed Findings
{% for finding in findings %}
{% if finding.status == "not-satisfied" %}
### {{ finding.control_id }}: {{ finding.title }}
**Status:** {{ finding.status }}
**Risk Level:** {{ finding.risk_level }}
**Observation:** {{ finding.observation }}
{% endif %}
{% endfor %}
Run with:
trestle author jinja -i assessment-report.md.j2 -o assessment-report.md -lut assessment-lookup.yaml
Prepare a lookup table with POA&M data:
# poam-lookup.yaml
system_name: "My Federal System"
report_date: "2024-03-15"
total_items: 5
open_items: 3
closed_items: 1
deviation_items: 1
risk_breakdown:
high: 2
moderate: 2
low: 1
poam_items:
- id: "POAM-001"
control: "AC-1"
title: "Outdated Access Control Policy"
risk_level: "High"
status: "remediating"
due_date: "2024-03-31"
milestones:
- title: "Draft updated policy"
due: "2024-03-15"
status: "complete"
- title: "Policy approved"
due: "2024-03-31"
status: "in-progress"
- id: "POAM-002"
control: "AU-2"
title:
Template for a POA&M status report:
---
title: POA&M Status Report - {{ system_name }}
date: {% md_datestamp format="%B %d, %Y" %}
---
# POA&M Status Report
**System:** {{ system_name }}
**Report Date:** {{ report_date }}
## Summary
| Status | Count |
|--------|-------|
| Open | {{ open_items }} |
| Closed | {{ closed_items }} |
| Deviation/Accepted | {{ deviation_items }} |
| **Total** | **{{ total_items }}** |
## Risk Breakdown
| Risk Level | Count |
|------------|-------|
| High | {{ risk_breakdown.high }} |
| Moderate | {{ risk_breakdown.moderate }} |
| Low | {{ risk_breakdown.low }} |
## Open Items
| ID | Control | Title | Risk | Status | Due Date |
|----|---------|-------|------|--------|----------|
{% for item in poam_items -%}
{% if item.status != "closed" -%}
| {{ item.id }} | {{ item.control }} | {{ item.title }} | {{ item.risk_level }} | {{ item.status }} | {{ item.due_date }} |
{% endif -%}
{% endfor %}
## Milestone Timeline
{% for item in poam_items %}
{% if item.status != "closed" %}
### {{ item.id }}: {{ item.control }} - {{ item.title }}
| Milestone | Due Date | Status |
|-----------|----------|--------|
{% for ms in item.milestones -%}
| {{ ms.title }} | {{ ms.due }} | {{ ms.status }} |
{% endfor %}
{% endif %}
{% endfor %}
Run with:
trestle author jinja -i poam-report.md.j2 -o poam-report.md -lut poam-lookup.yaml
Converted and distributed by TomeVault — claim your Tome and manage your conversions.