photocraft
Skill0 starsChanged 37 days agoMITView on GitHub
Use when editing images or automating the desktop in PhotoCraft, running headless PhotoCraft workflows, or setting up or troubleshooting its MCP server or CLI.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- midasmatterhorn/artcraft-skillstheir own version, first seen Oct 17, 2026
- hermes-pro/storytold-skillstheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- midasmatterhorn/artcraft-skills★ 66same name
- hermes-pro/storytold-skills★ 36same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anima-promptingSkill
- artcraftSkill
- electrobunSkill
- lanraragiSkill
- pixi-vnSkill
- spitballingSkill
- tolariaSkill
- tracker-boardSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 8
Use the installed app's interfaces as the authority.
- Distinctive: line 31
Look up each engine command before its first use.
- Distinctive: line 45
Layer state: check insertion position, resulting layer type, and active layer before the next operation.
- Distinctive: line 47
Recovery: after an error, partial batch, or lost reply, inspect what applied before retrying or continuing.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
PhotoCraft
Use the installed app's interfaces as the authority. Discover the commands and session behavior needed for the task; this skill supplies the editing workflow.
1. Choose the session
Identify the installed version, input, and intended output. With shell access, locate photocraft-cli on PATH or in the installation directory and read --help. With MCP, inspect its launch configuration and exposed schemas.
| Task | Route |
| Edit an open desktop document or drive the UI | Bridge MCP connected to that desktop, or its direct control protocol. |
| Edit independent files, convert formats, or process a folder | Headless CLI, even when live MCP is available. |
| Keep headless documents open across adaptive edits | Reuse headless MCP, or a persistent CLI serve session. |
| Headless work with MCP but no shell | Headless MCP. |
Establish the backend from its configuration and inspected state; matching tool names do not identify the session. Desktop and headless sessions have separate documents and histories. A saved layered file transfers a checkpoint between them, not unsaved state.
For connection setup or failure, CLI invocation, file access, or differences between live and headless capabilities, read Connection discovery.
Proceed when the intended session and input/output access are established. Preserve unsaved work before any required restart.
2. Inspect and discover
Inspect the target document, active layer, layer types and order, masks, and selection. Obtain ids from that session. Reinspect after switching documents or changing structure; interpret bounds using the schema of the interface returning them.
Look up each engine command before its first use. Discovery entry points:
- MCP:
command_list - CLI:
photocraft-cli commands --json - Direct protocol:
engine.commands
Use the installed interface's filtering when available; broaden the search when a parameter supplies the requested behavior rather than a separate command. Read parameter names, types, ranges, defaults, and availability conditions. A disabled command may require a document, selection, or different layer type. CLI arguments, MCP tool schemas, and engine parameters are separate contracts.
Proceed when the operation has a discovered command and an unambiguous target in the chosen backend.
3. Edit, verify, save
Make a small edit and inspect its result. Keep dependent edits in one session. Prefer adjustment layers and masks when editability matters.
- Layer state: check insertion position, resulting layer type, and active layer before the next operation.
- Selection state: establish the intended edit area; inspect the mask created with a new adjustment or fill layer rather than assuming its scope.
- Recovery: after an error, partial batch, or lost reply, inspect what applied before retrying or continuing. A success reply alone does not prove the intended change.
Render a preview of the target document and compare it with the requested result. Discover whether the chosen backend returns a document render or a window capture; use a supported alternative when needed.
For layered edits, save an editable master before flat exports. Discover save/export options for the chosen backend, wait for any returned jobs to finish, and inspect the saved structure and warnings. For conversion-only work, verify the requested output format and settings.
Done when the result is visually checked, required outputs are saved, and their paths, format loss, and any unverified behavior are reported.
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
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.