How do I install the Lang Generic skill?

Run npx skillmds@latest add xiaolai/lang-generic in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lang Generic safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lang Generic?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lang Generic free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lang Generic?

xiaolai (@xiaolai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lang Generic by xiaolai — Agent Skill

Name: Lang Generic
Author: xiaolai

File contents

Generic Language Adapter

Used when the project language is not recognized or not in the supported set. Applies best-effort heuristics.

Public API Detection Heuristics

Since we don't know the language's visibility rules, use these signals:

Signal	Likely Public	Confidence
`export` keyword present	Yes	High
`public` keyword present	Yes	High
`pub` keyword present	Yes	High
Uppercase first letter (Go-like)	Maybe	Medium
No underscore prefix	Maybe	Low
Defined at top-level / module scope	Likely	Medium

Symbol Detection

Look for common patterns across languages:

Pattern	Likely Symbol Type
`function name(` or `func name(` or `def name(` or `fn name(`	Function
`class Name`	Class
`struct Name`	Struct
`interface Name`	Interface
`type Name`	Type definition
`enum Name`	Enum
`const NAME` or `val NAME` or `let NAME` (UPPER_CASE)	Constant

Documentation Detection

Look for common doc comment patterns:

Pattern	Format
`/** ... */`	JSDoc / JavaDoc
`/// ...`	Rust-style / C# XML doc
`# ...` after `"""`	Python docstring
`// Name ...` (comment starting with symbol name)	Godoc-style
`""" ... """` or `''' ... '''`	Python docstring

Completeness Check

Since we can't parse language-specific documentation format, use a simpler check:

Has any comment: Symbol has a documentation comment directly above it
Non-trivial: Comment is more than 5 words
Mentions parameters: If function-like, comment mentions parameter names

Recommendations

When using the generic adapter, the agent should:

Flag that detection is heuristic-based (confidence: low)
Suggest the user configure language explicitly in config
Still attempt mapping and coverage analysis using available signals
Note any language-specific patterns it recognizes but can't fully parse

File Patterns

Source files: all files not matching known binary/config extensions Exclude: common non-source directories (node_modules/, vendor/, dist/, .git/)

---name: lang-genericdescription: Use when writing, auditing, or generating documentation for projects in unsupported languages — covers docstring conventions, API doc extraction, and generic heuristic patterns.---# Generic Language AdapterUsed when the project language is not recognized or not in the supported set. Applies best-effort heuristics.## Public API Detection HeuristicsSince we don't know the language's visibility rules, use these signals:| Signal | Likely Public | Confidence ||--------|--------------|------------|| `export` keyword present | Yes | High || `public` keyword present | Yes | High || `pub` keyword present | Yes | High || Uppercase first letter (Go-like) | Maybe | Medium || No underscore prefix | Maybe | Low || Defined at top-level / module scope | Likely | Medium |## Symbol DetectionLook for common patterns across languages:| Pattern | Likely Symbol Type ||---------|-------------------|| `function name(` or `func name(` or `def name(` or `fn name(` | Function || `class Name` | Class || `struct Name` | Struct || `interface Name` | Interface || `type Name` | Type definition || `enum Name` | Enum || `const NAME` or `val NAME` or `let NAME` (UPPER_CASE) | Constant |## Documentation DetectionLook for common doc comment patterns:| Pattern | Format ||---------|--------|| `/** ... */` | JSDoc / JavaDoc || `/// ...` | Rust-style / C# XML doc || `# ...` after `"""` | Python docstring || `// Name ...` (comment starting with symbol name) | Godoc-style || `""" ... """` or `''' ... '''` | Python docstring |## Completeness CheckSince we can't parse language-specific documentation format, use a simpler check:1. **Has any comment**: Symbol has a documentation comment directly above it2. **Non-trivial**: Comment is more than 5 words3. **Mentions parameters**: If function-like, comment mentions parameter names## RecommendationsWhen using the generic adapter, the agent should:1. Flag that detection is heuristic-based (confidence: low)2. Suggest the user configure `language` explicitly in config3. Still attempt mapping and coverage analysis using available signals4. Note any language-specific patterns it recognizes but can't fully parse## File PatternsSource files: all files not matching known binary/config extensionsExclude: common non-source directories (`node_modules/`, `vendor/`, `dist/`, `.git/`)

Frequently asked questions

Lang Generic