No Type In Docs

Name: No Type In Docs
Author: marius-townhouse

Checked

marius-townhouse·vlatest·writing

This skill automatically extracts text from documents without requiring manual typing, saving time and effort for data processing.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add marius-townhouse/effective-typescript-skills --skill no-type-in-docs -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

marius-townhouse

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 30 Sept 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned marius-townhouse/effective-typescript-skills at d754db2077.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: d754db2077
Manifest: skills/no-type-in-docs/SKILL.md
Scanned: 1 file, 216 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill allows AI agents to generate documentation without including TypeScript type annotations. It removes the noise of types from generated text, focusing solely on the descriptive aspects of code or configuration. This results in cleaner, more readable documentation for users who may not be familiar with TypeScript.

When to use it

Generating API reference documentation where type information is less relevant than usage examples.
Creating user-facing guides that should avoid technical jargon like type annotations.
Producing markdown documentation from code comments or docstrings, ensuring a simplified output.
Automating the creation of internal knowledge base articles for non-technical team members.

Key capabilities

Removes TypeScript type annotations from generated text.
Focuses on descriptive content during documentation generation.
Produces cleaner and more readable documentation.

Example prompts

"Generate markdown documentation for this function, excluding type information."
"Create a user guide explaining this configuration file without mentioning types."
"Document these code comments as a markdown article, removing all TypeScript annotations."

Tips & gotchas

This skill is most effective when the source material contains both descriptive text and TypeScript type annotations. Be aware that some information may be lost if it's solely conveyed through types.