layer-3d
Use when producing 3D assets with Layer: generating a mesh from text or an image, retopologising or remeshing, retexturing an existing mesh, rigging a character, or animating a rigged mesh. Also when choosing between quad and triangle output, setting a polygon budget, or asking for PBR textures for a game engine. Keywords: 3D, mesh, model, text to 3D, image to 3D, remesh, retopology, retexture, rig, skeleton, animate, PBR, quad mesh, poly count, glTF, FBX.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- layer-3d
- license
- MIT
- description
- Use when producing 3D assets with Layer: generating a mesh from text or an image, retopologising or remeshing, retexturing an existing mesh, rigging a character, or animating a rigged mesh. Also when choosing between quad and triangle output, setting a polygon budget, or asking for PBR textures for a game engine. Keywords: 3D, mesh, model, text to 3D, image to 3D, remesh, retopology, retexture, rig, skeleton, animate, PBR, quad mesh, poly count, glTF, FBX.
02 资源文件 1
- 参考文档skill-report.json34.8 KB
03 SKILL.md 正文
Layer 3D Generation
Overview
3D on Layer is a chain of separate use cases, not one call. Generate the mesh, then remesh, retexture,
rig, or animate it as the deliverable requires. Each stage is its own filter.use_case and its own
run, and each takes the previous stage's output file_id as input.
| Stage | filter.use_case |
Input |
|---|---|---|
| Mesh from a description | text_to_3d |
prompt |
| Mesh from concept art | image_to_3d |
init_image or reference_image |
| Cleaner topology, lower count | remesh |
init_mesh |
| New surfaces on an existing mesh | retexture |
init_mesh, often texture_image |
| Skeleton and weights | rig |
init_mesh |
| Motion on a rigged mesh | animate |
rigged init_mesh |
The loop and the spend gate are in the layer skill. If a sibling skill named here is missing from
your available skills, ask the user to install it (npx skills add layerai/skills --skill <name>);
unattended, proceed from tool schemas and flag the gap.
Start from an image
image_to_3d is the stronger path whenever the design is settled or settleable. A generated mesh
inherits its silhouette and surface detail from the reference, so approving a still first with
layer-image costs one cheap image run and removes most of the iteration from an expensive 3D one.
The reference image should show the subject clean: isolated on a plain background, lit evenly, in a three-quarter view that reveals depth. A dramatic, heavily shadowed key art frame makes a worse reference than a plain orthographic-ish view, because the model reads shadow as geometry.
text_to_3d is right when nothing exists yet and the shape is simple or generic enough to describe.
Say what the mesh is for
The engine target changes the request, so state it rather than accepting defaults:
- Topology:
quad_meshwhere the asset will be sculpted, deformed, or subdivided downstream. Triangles are fine for a static prop that ships as-is. - Budget: a
face_limitreflecting the platform. A hero prop on desktop and a background prop on mobile are different requests, and remeshing later costs another run. - Surfaces:
pbr_materialsandinclude_textureswhen the asset goes into a lit scene. Without them you get geometry and a flat surface, which reads as broken in an engine.
The per-model inference schema is the authority on which of these apply, so read get_base_model
before composing the run.
Describing geometry
3D prompts reward structural language and ignore atmosphere. Lighting, mood, and camera belong to an image prompt and do nothing here, because the mesh carries no lighting.
Name the form: overall silhouette, proportions, how parts join, surface material, and the level of detail. "Squat clay cooking pot, wide rounded belly, short flared neck, two small looped handles at the shoulder, hand-thrown surface with visible ridges" describes a mesh. "Beautiful ancient pot, dramatic lighting" describes a photograph and will produce a generic one.
Symmetry and closed forms generate reliably. Thin protrusions, chains, cloth, and hair are where generated meshes fail, so plan to model those separately or accept them as fused geometry.
Rigging and animation
rig produces a skeleton and weights, and it expects a mesh in a neutral, limbs-apart rest pose. A
mesh generated in a dynamic action pose rigs badly, so generate the rest pose first and animate into
the action.
animate needs a rigged mesh, so the two run in order. Where a model offers named motion presets,
those are more reliable than describing the motion in prose.
Worked example
"Turn this approved prop concept into a game-ready mesh for mobile."
- The concept exists from an earlier image run and already carries a
file_id. list_base_modelswithfilter.use_case: "image_to_3d"andfilter.capabilities: {textures: true}(an object of booleans, not a list of names). Take the first result, thenget_base_modelfor the fields it accepts.estimate_forge_pricewith the concept asimage_to_3dinput,pbr_materialsandinclude_textureson,quad_meshoff for a static prop, and aface_limitmatched to mobile. 3D runs are expensive, so expect this to clear 20 CUs and ask before proceeding.- Execute, poll at
poll_interval_seconds. - Inspect the result before chaining. If the silhouette is right but the count is too high, the next
run is
remeshon the outputfile_id, not a regenerate.
Common mistakes
- Using
text_to_3dwhen concept art exists or could be generated cheaply first. - Feeding a dramatic, shadow-heavy key art frame as the 3D reference.
- Writing an image prompt (lighting, mood, camera) for a mesh.
- Leaving topology, budget, and materials unspecified, then remeshing in a second paid run.
- Rigging a mesh generated in an action pose.
- Regenerating from scratch when
remeshorretexturewould fix the actual defect. - Expecting clean thin geometry such as chains, straps, or hair from a generated mesh.
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.