Resolve and validate jim file and path queries with strict input checks.
npx skills add https://github.com/JamSuite/jim --skill file-jamsuite
Please help me install this Agent Skill. Skill: file Source: https://github.com/JamSuite/jim/tree/main/skills/file Command: npx skills add https://github.com/JamSuite/jim --skill file-jamsuite
Inspect jim's file/path resolver outputs to determine existence, standardize naming, and derive canonical artifact paths.
Ask it to resolve a path like /jim:file exists docs/specs/jim/008-jimfile/spec.md.
High-intent search queries and answers about installing and using this skill.
To check if a spec or plan file path exists in jim, you can use the resolver to perform read-only existence checks and validation against your configured paths.
Slug normalization for file paths is the process of standardizing names into safe and predictable formats, ensuring consistent canonical artifact path discovery for specs, plans, research, and brainstorms.
You resolve canonical artifact paths for research and brainstorms by applying deterministic resolution and validation rules that rely on the jimconf.sh surface for configured paths.
Yes, you need jimconf.sh to compute the next-id and date generation for specs because the resolver relies on this configured surface to perform accurate path calculations.
A limitation of using Bash for file path resolution is that it performs strict, read-only path calculations, meaning it validates and calculates paths but does not modify or write artifacts directly.
Yes, you can use this path resolver to inspect deterministic outputs and derive date generation, next-id computation, and canonical artifact paths with strict input validation.
zb-ssConfigure Claude Code permissions and initialize workflow directories.
manishsinghmfGenerate the next OpenSpec artifact from ready artifacts using templates.
mark22013333Generate database designs and SQL artifacts from project specifications.
humanerd-drewValidate filesystem paths claimed in memory against actual state.
