skills.rest
tianjianjiang
tianjianjiangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

smith-placeholder

Standardize placeholder syntax in documentation and templates to prevent substitution errors.

1|Updated Nov 25, 2025
Search Tags:#templates#documentation#jinja2#syntax#prompts#placeholder
One-click install
npx skills add https://github.com/tianjianjiang/smith --skill smith-placeholder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smith-placeholder
Source: https://github.com/tianjianjiang/smith/tree/main/smith-placeholder
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-placeholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Placeholder syntax for documentation and prompts is standardized to prevent ambiguity and substitution errors when values are replaced in text and templates.

Core Features & Use Cases

  • Clear rules for inline placeholders and token naming to ensure consistent substitution across documents.
  • Forbidden patterns (like template injection risks) are documented to safeguard templates and code samples.
  • Use cases include technical docs, templates, API references, and knowledge bases where placeholders are substituted at render time.

Quick Start

Apply these rules to a sample document by replacing each placeholder with a clearly marked value.

Frequently Asked Questions about smith-placeholder

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

FAQPage Schema
How do I standardize placeholder syntax in documentation and prompts?▼

Standardize placeholder syntax by applying explicit inline, block, and code-sample guidelines that enforce consistent token naming and safe substitution across documents to prevent ambiguity and errors.

What is the best way to prevent template injection risks in documentation?▼

Preventing template injection in documentation requires enforcing safety constraints and documenting forbidden patterns to ensure placeholders are substituted safely and predictably during render time.

How do I create clear rules for inline placeholders and token naming in technical docs?▼

Create clear rules for inline placeholders by defining explicit token naming conventions and substitution guidelines that ensure consistent replacement of values across technical documents and knowledge bases.

Does this placeholder standardization approach work for API references and knowledge bases?▼

Yes, placeholder standardization works for API references and knowledge bases by applying predictable substitution guidelines to ensure values are safely replaced in text and templates at render time.

Can I use Jinja2 syntax for placeholder substitution in technical docs?▼

You can use Jinja2 syntax for placeholder substitution in technical docs, provided you follow explicit block and code-sample guidelines that enforce safety constraints to avoid template injection or data leakage.

Related Skills

Explore More Content & Communication Skills→
ProjAnvilProjAnvil
3

tech-documentation

Draft API and architecture documentation using standardized templates.

Official
Intermediate
faisalanjumfaisalanjum
3

test-re-arguments

Test substitution of dynamic arguments into the $ARGUMENTS variable.

Community
Basic
lbliiilbliii
41

bengal-content-migration

Migrates static site and Markdown content to Bengal format.

Community
Intermediate
aurumorincaurumorinc

write-script-postgresql

Create parameterized PostgreSQL queries using a structured template.

Official
Basic