history vs frontend-api-contracts
history and frontend-api-contracts are both ai and llm tools skills. frontend-api-contracts scores higher (84 vs 77 out of 100). frontend-api-contracts has more GitHub stars (91k), and frontend-api-contracts was updated more recently (2 days ago). The table compares them side by side.
| history | frontend-api-contracts | |
|---|---|---|
| Score | 77 / 100 | 84 / 100 |
| What it does | Draft a new history entry, or update the most recent one with `--update`. Use after a meaningful commit or set of commits. Provide the "why" as an argument — /history the reason this change was made. Use /history --update to extend the latest entry without prompting. | This skill should be used when the user asks to "add an API call", "change a backend", "update settings persistence", "change conversation events", "fix backend auth", "add Agent Server support", or changes src/api, backend registry, Cloud/runtime transport, settings, secrets, compatibility, or conversation resume behavior. |
| Publisher | Community: cosmosgl | Community: OpenHands |
| Grades | Maintenance A, Licence A, Quality A | Maintenance A, Licence A, Quality A |
| npm downloads a week | Not on npm | Not on npm |
| Runs | Skill | Skill |
| Works with | Claude Code, Claude apps | Claude Code, Claude apps |
| GitHub stars | 1,300 | 91,343 |
| Last commit | 16 Oct 2026 | 20 Oct 2026 |
| Licence | MIT | MIT |
| Listed since | 19 Oct 2026 | 20 Oct 2026 |
| Install history | Install frontend-api-contracts |
Questions
Is history or frontend-api-contracts more popular?
frontend-api-contracts has more GitHub stars: 91,343.
Can I use history and frontend-api-contracts together?
Yes. AI assistants can load several skills at once. Install both and the assistant picks the right one for each task.