Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This skill set packs 86 tools for the daily routines of software teams: commit discipline, standup and Jira workflows, C4 and Mermaid diagrams, test plans with Figma validation, design tokens, dependency management, and cross-team handoff documentation. It lets developers, project managers, QA engineers, and designers work through a single agent that knows the full cycle.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
I’m using
Quick install with skills CLI
Installs: Run the documented repository quick installer; the source does not establish which individual skills it selects. · Claude Code, Codex, Cursor, AdaL
Before you start
Node.js with npx available.
Run the repository quick-install command in a terminal.
Installs: Skills only; installs the selected crafting-effective-readmes folder. · Claude Code
Before you start
A local copy of the softaworks/agent-toolkit repository
Run from: softaworks/agent-toolkit repository root
In the terminal command below, replace the author-provided `<skill-name>` placeholder with `crafting-effective-readmes`, then run it from the repository root.
Path to the README; `[path/to/README.md]` is a placeholder
Project type or intended audience
Use the crafting-effective-readmes skill to review `[path/to/README.md]` for `[project type: open source, personal, internal, or config]`. Compare it with the current project state, flag stale or missing sections, and propose a short list of specific edits without changing the file. Replace the bracketed values with the actual README path and project type.
Path to one React component; `[path/to/component.tsx]` is a placeholder
Use the react-useeffect skill to review `[path/to/component.tsx]`. For each useEffect, say whether it synchronizes with an external system or can be replaced by calculation during render, useMemo, a key prop, an event handler, or another documented alternative. Suggest changes only; do not edit the file. Replace `[path/to/component.tsx]` with the component's actual path.
Whether one commit or multiple commits is preferred; multiple small commits is the documented default when unrelated changes exist
Required scopes or maximum subject length; `[scope rules or none]` is a placeholder
Use the commit-work skill to inspect the current working-tree diff, propose logical commit boundaries, and draft Conventional Commit messages with a one- or two-sentence what/why summary for each. Do not stage or commit anything. Use `[scope rules or none]` for any required scopes or subject-length rules.
Claude
Codex
Cursor
Gemini CLI
Copilot