list

List Heimdall configuration lock blocks with unlock phrases and targets.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/thomfilg/ai-plugin-work --skill list-thomfilg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list
Source: https://github.com/thomfilg/ai-plugin-work/tree/main/plugins/heimdall/skills/list
Command: npx skills add https://github.com/thomfilg/ai-plugin-work --skill list-thomfilg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the listing of Heimdall lock blocks, providing a streamlined way to view protected files and their configurations.

Core Features & Use Cases

  • Automated List Generation: Generates a list of active Heimdall stores, their lock blocks, unlock phrases, and resolved file/directory targets.
  • User-Friendly: Designed for users who want to quickly inspect or audit what's locked within their Heimdall configuration.
  • Use Case: For system administrators responsible for managing security and file protection within their repositories.

Quick Start

Run the 'list' skill to display the Heimdall lock blocks: /list

Frequently Asked Questions about list

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

FAQPage Schema
How do I list Heimdall lock block configurations for security auditing?

Listing Heimdall lock blocks requires a Bash environment within an active Heimdall configuration, where the script reads existing stores and outputs their lock blocks, unlock phrases, and file targets.

Can I view unlock phrases and protected file targets in Heimdall stores?

Yes, viewing unlock phrases and protected file targets in Heimdall stores is possible by generating an automated list that maps each lock block to its unlock phrase and resolved file or directory targets.

What is the best way to audit file protection configurations in a Heimdall environment?

The best way to audit file protection configurations in a Heimdall environment is to automate the listing of lock blocks, which streamlines the inspection of protected files, unlock phrases, and directory targets.

Does listing Heimdall lock blocks require any specific dependencies?

Listing Heimdall lock blocks requires a Bash environment within an active Heimdall configuration, but it does not require any additional external dependencies or packages to generate the lock block output.

Why should I use an automated script instead of manually checking Heimdall protected files?

You should use an automated script instead of manually checking Heimdall protected files because it provides a streamlined, user-friendly way to quickly inspect and audit all active stores and their lock configurations.