agentleFS
arjun988arjun988/blender-skills/.claude/skills/character-artist/SKILL.md

character-artist

Skill2.2k starsChanged 4 months agoMITView on GitHub

AAA character modeling for human anatomy, stylization, facial topology, clothing, hair, and animation-ready meshes. Use for game characters, facial expressions, and production character assets in Blender via MCP.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 8 mentionsNov 2026: 3 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the arjun988/blender-skills repository that our weekly crawl found: only 12 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always block proportions before detail.

    line 42
  2. Distinctive:

    No poles on primary deformation areas (relocate to hidden zones)

    line 85
  3. Distinctive:

    Create base mannequin/blockout via MCP

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Character Artist

Production character modeling with animation-ready topology. Anatomy-accurate or intentionally stylized.

When to Use

  • Human/humanoid character creation
  • Facial topology for expressions
  • Clothing and accessory modeling
  • Hair card systems or stylized hair
  • Character proportion and stylization

Workflow

Reference → Proportion Blockout → Body Forms → Limb Connection
    → Facial Features → Edge Loop Planning → Detail Pass
    → Clothing (separate mesh) → UV Handoff → Rig Handoff

Proportion Standards

TypeHead UnitsNotes
Realistic adult7.5–8 headsHero characters
Stylized4–6 headsExaggerated features
Heroic8–9 headsAction games

Always block proportions before detail.

Edge Loop Strategy

Critical loop locations:

  • Eyes: concentric loops for blink/expression
  • Mouth: 3-loop minimum for lip deformation
  • Jaw: loop following jaw line for open/close
  • Shoulders: deltoid loop for arm raise
  • Elbows/knees: 3-loop pinching pattern
  • Hips: loop for leg spread

See references/facial-topology.md for face-specific loops.

Facial Structure

  • Eye socket: recessed; brow ridge defined
  • Nose: bridge width matches inner eye distance (realistic)
  • Mouth: lower lip fuller than upper (realistic)
  • Ear: aligns eye brow to nose base
  • Skull underlying forms visible in stylization

Clothing Workflow

  1. Model body first (or use mannequin)
  2. Duplicate body faces for clothing base
  3. Solidify/extrude for cloth thickness
  4. Separate mesh: SM_Char_[Name]_Body, SM_Char_[Name]_Cloth_[Piece]
  5. Cloth does NOT share UVs with body
  6. Weight paint transfers from body (via rigging skill)

Hair Approaches

MethodUse CaseSkill
Hair cardsGame-realisticuv-workflow + texture-workflow
Strand curvesCinematicparticle/curve systems
Stylized meshLowpoly/stylizedblender-modeler
SculptedHero bakesculpting → retopology

Animation-Ready Requirements

  • Quad-dominant topology on deformation zones
  • No poles on primary deformation areas (relocate to hidden zones)
  • Even edge length in face/neck/joints
  • Separate objects for swap-able parts (head, hands, gear)

MCP Integration

  1. Create base mannequin/blockout via MCP
  2. Build body with mirror modifier via MCP
  3. Query topology (face count, edge flow) at checkpoints
  4. Separate clothing meshes via MCP
  5. Organize character collection hierarchy

Constraints

MUST DO

  • Establish proportions before facial detail
  • Plan edge loops for planned deformations
  • Separate clothing/accessories as unique meshes
  • Match style skill direction (stylized vs realistic)
  • Validate topology before rigging handoff

MUST NOT DO

  • Triangles on primary deformation surfaces
  • Poles at corner of mouth or inner eye
  • Single mesh for body + hard surface armor (separate)
  • Skip reference for facial likeness work
  • Over-poly face before LOD planning

Reference Guide

TopicReferenceLoad When
Facial topologyreferences/facial-topology.mdFace modeling
Body proportionsreferences/body-proportions.mdBlockout
Pipeline../references/asset-pipeline.mdPhase context

Style Integration

StyleAdjustment
realistic-styleFull anatomy; 8-head proportion
stylized-styleExaggerated features; 4–5 heads
lowpoly-styleMinimal loops; painted detail
horror-styleUncanny proportions; asymmetry

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.