One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill linguistics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linguistics
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/linguistics
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill linguistics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents ambiguous or misleading software names, UI text, and error messages by enforcing linguistic precision for meaning, audience register, and blame-free actionability.

Core Features & Use Cases

  • Morphology for software artifacts: Guides how to form compounds, choose abbreviations responsibly, and align identifier/label structure with the artifact kind.
  • Polysemy resolution: Forces ambiguous terms (e.g., provider, margin, shipping) to be qualified with domain-specific meaning to avoid comprehension failures.
  • Register selection for audiences: Ensures end-user, agent, and developer-facing language uses the right tone, vocabulary density, and structure.
  • Error-message linguistics: Applies a What → Why → What-to-do structure that is specific, blame-free, and action-oriented.
  • Cross-cultural language awareness: Flags linguistic facts that affect global readability and i18n decisions (number structure, plural agreement, script direction, currency meaning).

Quick Start

Use the linguistics skill when you need to revise an identifier, UI label, or error message so its meaning is unambiguous for your intended audience.

Frequently Asked Questions about linguistics

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

FAQPage Schema
How do I resolve ambiguous terms in UI labels and software identifiers?

To resolve ambiguous terms in UI labels, you must qualify polysemous words like provider or margin with domain-specific meaning. This prevents comprehension failures by enforcing linguistic precision for meaning and audience register across end-user and developer contexts.

What is the best way to write blame-free error messages for software users?

Writing blame-free error messages requires applying a What → Why → What-to-do linguistic structure. This approach ensures your error wording is specific, action-oriented, and avoids blaming the user for the failure.

How do I choose the right audience register for developer and end-user facing text?

Choosing the right audience register involves aligning tone, vocabulary density, and structure with the specific target audience. You must evaluate whether the text targets end-users, agents, or developers to ensure appropriate linguistic fit.

How does morphology affect software artifact naming and abbreviations?

Morphology affects software artifact naming by guiding how you form compounds and choose abbreviations responsibly. Proper morphological alignment ensures your identifier and label structure matches the specific artifact kind.

Does cross-cultural language awareness affect internationalization decisions?

Cross-cultural language awareness directly affects internationalization by flagging linguistic facts like number structure, plural agreement, and script direction. Addressing these facts ensures global readability and portable clarity before i18n implementation.