sybil-solutions / inference-optimisation-skill
Agent skill for hill-climbing local LLM serving speed (decode, speculative decoding, prefill, KV, startup, TTFT) on any hardware and quantization
- Stars
- 1,259 stars
- Forks
- 114 forks
- Language
- Python
- License
- MIT
- Created
- Nov 16, 2026
- Last push
- Nov 16, 2026
- Updated
- Nov 20, 2026
Why these Tags: an agent read the README and quoted it
- Agent skill from the readme:
An agent skill for **hill-climbing the speed of a local LLM server** on any hardware and any quantization.
- Benchmarking from the readme:
`bench.py` benchmarks any OpenAI-compatible server.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 17, 2026: +682 stars in 7 days.
Star History
4 days recorded, Nov 16, 2026 – Nov 19, 2026 (UTC). Net change +1,317 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/sybil-solutions/inference-optimisation-skill) Badge
[](https://awesomerepos.com/sybil-solutions/inference-optimisation-skill) Timeline
It gained stars on each of the 4 days recorded since Nov 16, 2026.
- Created on the Repository Host
- Reached 100 stars, on the day it was created
- +406 stars in one day
- Latest push
- Entered the Repository Index: +682 stars in 7 days
- Reached 500 stars, 1 day after it was created
- Largest star day recorded: +579 stars
- Reached 1,000 stars, 2 days after it was created
- +180 stars in one day
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 3 Observations, Nov 18, 2026 – Nov 20, 2026. Forks +33. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 19, 2026: no new push
- Nov 20, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 19, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 3 tasks for the maintainers of sybil-solutions/inference-optimisation-skill.
Improve the Health Facts of the GitHub repository sybil-solutions/inference-optimisation-skill. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/sybil-solutions/inference-optimisation-skill. A change to the repository can improve each of the 3 items below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: No GitHub release (read on 2026-11-17). Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. 2. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-19). Rule: The root of the default branch has a file named CHANGELOG, CHANGES, HISTORY, NEWS, RELEASE, or RELEASES, with no extension or with .md, .markdown, .rst, .txt, or .adoc. Release notes on GitHub releases do not count. Task: Add CHANGELOG.md at the root of the default branch. Write one section for each published release, newest first, from the GitHub releases, the Git tags, and the commit history. Do not invent changes. If the project uses a release tool (for example Changesets, release-please, or semantic-release), configure it to update this file for each release. 3. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-19). Rule: GitHub finds a security policy (SECURITY.md in the repository or in the owner's .github repository). Task: Add SECURITY.md at the root or in .github/. Say which versions get security fixes and how to report a vulnerability privately. If GitHub private vulnerability reporting is on, point to it. Ask me for the contact; do not invent one. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
3 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-16, 3 days ago. Source
-
Yes: Commits in the last 13 weeks
1 commit on the default branch in the last 13 weeks (GitHub, 2026-11-19). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 1 of the last 52 weeks (GitHub, 2026-11-19). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 1
Releases
0 of 3 checks (1 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-17). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
No: A changelog file at the root
No changelog file at the root (GitHub, 2026-11-19).
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-19).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
3 of 3 checksDependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 19, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 20, 2026: 1,259 stars, 114 forks, last push Nov 16, 2026, not archived. One of 3 Observations since Nov 18, 2026.