Skip to content
TrustedSkillsbeta
Back to all skills

Type Design Analyzer

Checked
paulkinlan·vlatest·frontend·Apache-2.0

Analyzes design elements like typography, layout, and color palettes to identify strengths and areas for improvement.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add paulkinlan/co-do --skill type-design-analyzer -a claude-code

  2. 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

paulkinlan

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

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 paulkinlan/co-do at d3ebdbd506.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d3ebdbd506
Manifest
.claude/skills/type-design-analyzer/SKILL.md
Scanned
1 file, 95 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

The paulkinlan-type-design-analyzer skill analyzes type designs, providing insights and feedback. It can assess aspects of font design such as kerning, hinting, and overall visual appeal. This allows users to improve the quality and usability of their typography projects.

When to use it

  • You're a font designer seeking automated critique on your work.
  • You’re working on a branding project and need an objective assessment of a typeface choice.
  • You want to evaluate the readability and accessibility of text in a design mockup.
  • You are creating digital assets and require feedback on hinting quality for optimal rendering across devices.

Key capabilities

  • Type design analysis
  • Kerning evaluation
  • Hinting assessment
  • Visual appeal critique

Example prompts

  • "Analyze this font file and provide feedback on kerning pairs."
  • "Evaluate the readability of this text sample using [font name]."
  • "Assess the hinting quality of this OpenType font."

Tips & gotchas

The skill's effectiveness depends on providing valid font files as input. Results should be considered suggestions for improvement, not definitive judgments.