editorial-portfolio-chapters
Create or redesign creative-studio, agency, photographer, artist, and portfolio websites where project work leads the story.
Install / Use
npx skills add MengTo/Skills --skill editorial-portfolio-chaptersInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of editorial-portfolio-chapters
editorial-portfolio-chapters scores 85/100 on our quality scale, 422nd of 642 Marketing skills we index.
Its SKILL.md is 4.4 KB long, well organised into 11 sections and no code examples: a solid amount of guidance for an agent.
With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so editorial-portfolio-chapters is actively maintained.
- Our last check on 2026-11-04 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
editorial-portfolio-chapters compared with similar skills
All 4 of these similar skills score higher than editorial-portfolio-chapters; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| editorial-portfolio-chapters (this skill)by MengTo | 85 | 6.3k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| LocalAIby mudler | 100 | 50.4k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
Frequently asked questions
- How do I install editorial-portfolio-chapters?
- Run
npx skills add MengTo/Skills --skill editorial-portfolio-chapters. The install tabs above show the steps for each supported agent. - Which AI agents does editorial-portfolio-chapters work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is editorial-portfolio-chapters safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is editorial-portfolio-chapters still maintained?
- The repository was last updated about 2 months ago, so editorial-portfolio-chapters is actively maintained.
Skill content
View source on GitHubname: editorial-portfolio-chapters description: Create or redesign creative-studio, agency, photographer, artist, and portfolio websites where project work leads the story. Use for dark editorial shells, full-bleed campaign media, color-coded case-study chapters, oversized service typography, restrained project reveals, and a decisive contact finale.
Editorial Portfolio Chapters
Build the page as a sequence of distinct editorial chapters. Let the work establish desire before explaining the studio.
Establish the Story
- Open with one strong campaign image and a concise positioning line.
- Move directly into selected work. Treat each case study as a new magazine cover.
- Explain the studio point of view only after the work has earned attention.
- Use oversized service typography as the handoff from proof to contact.
- End with a high-contrast contact chapter that feels final, not appended.
Replace all source brands, projects, people, claims, images, labels, and links with original or client-provided content. Preserve pacing and hierarchy, not source content.
Build the Visual System
- Frame the page with near-black, then introduce warm white and one muted color field per project.
- Use a grotesk display face with a neutral text companion. Keep labels compact and copy readable.
- Align to a 12-column grid with 40–64px desktop edge margins.
- Favor square or deliberately cropped media, restrained radii, hairline rules, and almost no shadow.
- Let the strongest proof change scale. Do not turn every section into a hero or bento grid.
- Keep full-bleed chapters rare and purposeful.
Compose the Page
- Header: place compact navigation at the outer edges and keep the identity centered or strongly anchored.
- Hero: reserve most of the first viewport for one stable image; expose the first project below the fold.
- Projects: alternate dark framing with muted color panels; show title, role, year, and action without hover.
- Studio: use an asymmetrical portrait or process composition instead of a generic team-card grid.
- Services: set capabilities as large semantic headings or links with controlled wrapping.
- Contact: switch to one unmistakable signal color and one primary action.
- Footer: resolve navigation, location, social links, and legal text without competing with the contact ask.
Implement the Signature Interactions
Editorial project panel reveal
- Reserve the panel height before media loads.
- Clip only the image layer; keep title and metadata selectable.
- Reveal with a 500–760ms mask or shallow translate.
- On hover or focus, scale media no more than
1.02and expose the same project action. - Keep every panel understandable when static.
Oversized service handoff
- Use
clamp()for scale and a short edge-aligned text mask. - Shift weight, underline, or tone on hover and focus without moving layout.
- Open optional details with semantic disclosure behavior, Escape support, and focus return.
- Wrap deliberately on mobile and render immediately under reduced motion.
Motion Defaults
- Use 160–220ms for control feedback and 500–760ms for section entrances.
- Stagger direct children by 45–70ms with
cubic-bezier(.22,.61,.36,1). - Keep parallax below 5% and the hero stable enough to study.
- Tie navigation or background changes to section boundaries.
- Pause offscreen media and observers; clean up timelines on route changes.
- Do not hijack scroll.
Validate
- Confirm logical heading order, visible focus, useful alt text, and contrast through every color change.
- Test keyboard, touch, 200% zoom, narrow mobile, slow media, missing media, and reduced motion.
- Confirm case studies remain readable before animation and no source content was lightly paraphrased.
- Remove invented awards, clients, outcomes, or claims when evidence is unavailable.
Source-Backed Prompt Pack
Use Mara Voss Interaction Prompt Pack as a worked example for turning one editorial portfolio into portable loader, pinned chapter, archive, inspection, sticky-stack, and footer interaction prompts. Reuse the motion logic, not the reference identity, copy, imagery, or claims.
Avoid
- Explaining the studio before showing its work.
- Repeating identical rounded cards across every chapter.
- Fast card choreography, large parallax, or decorative motion loops.
- Hiding project titles or actions until hover.
- Copying source imagery, brand language, project names, or client claims.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
LocalAI
50.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
