self-marketing-lint

Detect promotional language in Forge Harness documentation and metadata.

7|Updated May 26, 2026
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill self-marketing-lint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-marketing-lint
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-meta/skills/self-marketing-lint
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill self-marketing-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This deprecated skill previously solved the problem of inconsistent, overly promotional language in Forge Harness project documentation and file metadata that reduces clarity and professionalism. Its functionality has been merged into the harness-doctor --lint mode as of 2026-06-02.

Core Features & Use Cases

  • Promotional Language Detection: Scans project files for self-marketing phrases, overly positive cushion words, and unsubstantiated version brag patterns (now handled by harness-doctor Step 3-L).
  • Documentation Standardization: Helps maintain neutral, consistent tone across all project documentation and description fields in a Forge Harness portfolio (now handled by harness-doctor Step 3-L).
  • Use Case: A project maintainer could previously use this skill to audit all README and track files in their Forge Harness project to remove phrases like "industry-leading" or "the best version ever" to align with team documentation standards.

Quick Start

Use the self-marketing-lint skill to scan all project documentation files for self-promotional language and cushion words.

Frequently Asked Questions about self-marketing-lint

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

FAQPage Schema
How do I detect self-marketing language in project documentation?

To detect self-marketing language in project documentation, use this skill to scan README files and metadata for promotional phrases, cushion words, and version brag patterns. This ensures a neutral, professional tone across Forge Harness portfolios.

How do I scan Forge Harness track files for promotional phrases?

Scanning Forge Harness track files for promotional phrases involves checking the project metadata and description fields for overly positive cushion words. This process was previously handled by this skill but is now integrated into harness-doctor Step 3-L.

What is the best way to standardize documentation tone across a project portfolio?

Standardizing documentation tone across a project portfolio is achieved by auditing files to remove self-promotional language and unsubstantiated version brags. The process enforces neutral, consistent standards, now managed by harness-doctor --lint mode.

Does the self-marketing-lint skill still work for auditing README files?

The self-marketing-lint skill is deprecated and no longer actively works for auditing README files. Its functionality for detecting inconsistent promotional language was merged into the harness-doctor --lint mode as of 2026-06-02.

Why should I remove cushion words from project metadata?

Removing cushion words from project metadata is necessary because overly positive language reduces clarity and professionalism. Maintaining neutral documentation standards ensures consistency across all Forge Harness project portfolios.