list

Enumerate available Trigent standards and application profiles with ready-to-run view and load commands.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill list-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/standards/skills/list
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill list-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with a large set of coding standards and application profiles, it is hard to know exactly which ones exist, who owns them, and what command loads each one. This Skill scans the standards reference directory and produces a complete command reference so you never have to guess. ## Core Features & Use Cases - Standards Discovery: Globs the technical-guidance directory for standard files, reads each file's frontmatter, and extracts owner and scope metadata. - Application Profile Discovery: Finds profile files following the {parent}-{profile-name}-profile.md naming convention and derives parent standard and profile argument names. - Command Reference Output: Renders Markdown tables mapping every standard and profile to its /standards:view and /standards:load commands, plus repo-level audit commands. - Use Case: You join a repository and want to know which Trigent standards apply. Run the list command to see every standard and profile with its scope, owner, and the exact command to load it. ## Quick Start Ask the assistant to list all available Trigent standards and application profiles with their view and load commands.

Frequently Asked Questions about list

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

FAQPage Schema
How do I list all available Trigent standards?

Run the list command, which globs the technical-guidance references directory for standard Markdown files. It reads each file's frontmatter to extract owner and scope, then displays a table with view and load commands for each standard.

How do I find application profiles for a specific standard?

The list output includes an Application Profiles table grouped by parent standard. Profiles follow the filename pattern parent-profile-name-profile.md, and each row shows the exact /standards:view and /standards:load commands with parent and profile arguments.

What metadata does the standards list show for each entry?

Each standard row shows its argument name, scope, and owner extracted from the file frontmatter. Application profile rows additionally derive the parent standard and profile argument from the filename, and include version-range when present.

Can I audit my repo against the listed standards?

Yes, the output includes repo commands such as /standards:audit for full conformance checks, --staged for staged changes, --branch for branch changes, and --mr for auditing a GitLab merge request.

Why is a standard file missing from the list output?

Files named detection-logic.md and anything under application-profiles are excluded from the standards table, and README.md is excluded from profiles. Verify the file is a standard Markdown file with valid frontmatter in the technical-guidance directory.