Ask Emil reads the skill you are about to use before recommending it, then points to one skill or one short sequence for the situation you describe. Its guide groups the repository into a main flow from idea to ship, upkeep skills for an existing codebase, references that sit underneath, standalone skills and a list of common situations. It is set to run only when you invoke it.
What You Get
- One recommended skill or short sequence with the reason
- A map of the main flow: prototype, build, break, review and learn
- An upkeep list for auditing, finding opportunities and removing motion
- Common situations matched to skills
Common Use Cases
- Choosing between animate, choreograph and gestures for a new piece of UI
- Deciding what to run before shipping a feature
- Finding the right audit skill for an app that feels off
What Makes It Unique
It carries no design rules of its own. Its value is the map: which skill leads the build, which checks follow, and which upkeep skills suit an existing app. It reads each target skill before describing it, so a recommendation reflects what that skill says today.
Under The Hood
One SKILL.md with no scripts or network access, set so the model only loads it when you invoke it by name. The model reads the SKILL.md of the skill it is about to recommend, matches your situation to the flow and replies with a recommendation.