ascii-motd-profile-banner

When to use this skill

CRITICAL TRIGGER RULE

• Use this skill ONLY when the user explicitly mentions the exact skill name: ascii-motd-profile-banner.

Trigger phrases include:

• "ascii-motd-profile-banner"
• "use ascii-motd-profile-banner"
• "Generate an SSH login welcome with ascii-motd-profile-banner"
• "Use ascii-motd-profile-banner to output MOTD (short version/long version)"

Boundary

• Produce templates and placement guidance only; do not modify system files.
• Never include sensitive information (tokens, internal URLs, account details, personal data).
• Default output is ASCII-only; ANSI color is optional and must have a no-color fallback.

How to use this skill

Inputs

• title (required)
• messageBullets (1–5 bullet points, required)
• mode (short | long, default short)
• width (default 80)
• includeLinks (optional: Docs / Tickets / Repo)
• colorMode (none | ansi256, default none)
• quietHint (default true: recommend quiet output for non-interactive shells)

Outputs (required)

• bannerShort (<= 12 lines)
• bannerLong (<= 30 lines)
• safetyNotes (>= 3 actionable security notes)
• toggleAdvice (interactive vs non-interactive display guidance)

Examples

• examples/ssh-short.md
• examples/ssh-long.md

Quality checklist

1. Short mode does not spam (<= 12 lines)
2. Copy/paste safe (no trailing spaces)
3. Security notes are clear, short, and actionable

Keywords

English: ascii-motd-profile-banner, motd, ssh banner, profile, welcome message, security notice, terminal Chinese: ascii-motd-profile-banner, MOTD, SSH Banner, login welcome, Profile, security notice, terminal

Common Gotchas

1. Version Compatibility: Pay attention to the compatibility between the framework version and dependency libraries; APIs may differ across versions
2. Configuration File Format: Configuration file format errors are the most common issue; it is recommended to use the editor's syntax check
3. Environment Variables: Ensure all necessary environment variables are set correctly, and do not hard-code sensitive information
4. Dependency Conflicts: When multiple versions coexist, watch out for dependency conflicts and use a lock file to pin versions
5. Performance Pitfalls: Pay attention to performance optimization in large-data scenarios, and avoid common issues such as N+1 queries

Usage Workflow

Step 1: Environment Preparation

Make sure the necessary dependencies and tools are installed in the development environment.

Step 2: Configuration Initialization

Perform basic configuration according to project requirements.

Step 3: Using Core Features

Implement the core functionality according to the sample code.

Step 4: Test Verification

Run tests to ensure the functionality works properly.

Step 5: Deployment and Launch

After development is complete, proceed with deployment and monitoring.