Awesome-omni-skill treido-skillsmith
Skill-system maintainer for Treido. Use to create/merge/trim skills, enforce treido-* naming, and keep `.codex/skills` minimal and consistent.
install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data-ai/treido-skillsmith" ~/.claude/skills/diegosouzapw-awesome-omni-skill-treido-skillsmith-6a8aa0 && rm -rf "$T"
manifest:
skills/data-ai/treido-skillsmith/SKILL.mdsource content
treido-skillsmith
Build and maintain Treido’s skill fleet as a small set of high-signal specialists.
When to Apply
- Creating a new
skilltreido-* - Consolidating overlapping skills
- Upgrading a skill to include
,references/
,templates/
, orrules/
(optional)scripts/ - Cleaning old skills and reducing bloat
Non-Negotiables
- Treido-maintained skills must be
treido-* - Keep skill instructions knowledge-heavy (avoid command spam)
- Prefer progressive disclosure: short core rules in
, details inSKILL.mdreferences/ - Stable documentation belongs in
/docs/
Standard Skill Skeleton
Every
treido-* skill should have:
- Frontmatter:
,namedescription - When to Apply / When NOT to Apply
- Non-negotiables (links to
+ SSOT docs)treido-rails - Output template (predictable deliverable)
- Minimal “violations” checklist
- References section (to
+ key repo files)/docs/
Cleanup Rules
- Delete vendor/third-party skills from
once their content is materialized into.codex/skillstreido-* - Keep
out of the critical path (skills must not depend on junction targets).agents
FORBIDDEN — Never Create These Folders
DO NOT create, copy, or mirror skills to:
,.agent/
,.agents/
,.cursor/
,.gemini/
,.kiro/
,.qoder/
,.qwen/
,.trae/.windsurf/
This repo uses
.claude/ and .codex/ ONLY. Do not "support other AI tools" by creating their folders.