> For the complete documentation index, see [llms.txt](https://docs.animeoshi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.animeoshi.com/how-rating-works/rating-attributes.md). # Rating Attributes ## In one sentence Rating Attributes are the five dimensions a Scout can score on each AnimeOshi episode - Soundtrack, Visual, Emotion, Writing, and Impact - which are surfaced as a five-axis radar so the *shape* of an episode's score is visible, not just the overall number. ## Overview A single overall score tells you *how good* an episode was, but not *why*. The Rating Attributes break that judgment into five fixed dimensions, so a great soundtrack episode reads differently from a great writing episode. They sit alongside the 1–5 star score in the rating flow and feed the attribute radar on each episode page. ## Details ### The five attributes AnimeOshi uses one fixed, global default set of five Rating Attributes. They are the same on every episode: | Attribute | What it measures | | -------------- | ---------------------------------------------- | | **Soundtrack** | Music quality and how well it fits the episode | | **Visual** | Animation quality | | **Emotion** | Emotional impact | | **Writing** | Story and dialogue quality | | **Impact** | Overall significance of the episode | ### How they relate to the OshiMeter When a fan rates an episode, they give a 1–5 star score and can optionally score the five attributes. The star score feeds the episode's OshiMeter (the headline number, stored 0–100 and usually shown as a 0–10 score). The attribute scores are aggregated separately and surfaced as their own averages, so the OshiMeter answers "how good?" while the attributes answer "good at what?" ### The attribute radar On the episode page, the five attribute averages are drawn as a five-axis radar chart. The shape of that radar is the quick read: a spike on Visual and Soundtrack with a dip on Writing tells you it was a spectacle episode that was light on story, even if the overall OshiMeter is the same as a quieter, writing-driven episode. Seeing the shape, not just the number, is the point of breaking the score into attributes. ### Why these five, fixed for everyone The attribute set is a fixed global default rather than something each anime or user configures. Keeping the same five dimensions across every episode means attribute scores are comparable site-wide: a high Emotion episode of one series can be read against a high Emotion episode of another, because both were scored on the same axis. ## FAQ **Q: What does "Emotion" mean as a rating attribute?** Emotion is short for emotional impact. How strongly the episode landed emotionally. It is one of the five Rating Attributes, alongside Soundtrack, Visual, Writing, and Impact. **Q: What is the difference between "Emotion" and "Impact"?** Emotion measures the episode's emotional impact specifically, while Impact measures its overall significance. How much the episode mattered to the series or stuck with you beyond the emotional beat. **Q: Do I have to score all five attributes when I rate an episode?** No. The 1–5 star score is the required input; scoring the five attributes is optional. Scoring them adds detail to the episode's attribute radar. **Q: Can the set of attributes change per anime?** No. The five Rating Attributes are a fixed global default and are the same on every episode, which keeps attribute scores comparable across the whole site. ## Related pages * [What is the OshiMeter?](/core-concepts/oshimeter.md) * [How to Rate Episodes on AnimeOshi](/how-rating-works/how-to-rate-episodes.md) * [Watch If / Skip If](/core-concepts/watch-if-skip-if.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.animeoshi.com/how-rating-works/rating-attributes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.