curl -s -H "User-Agent: `adom-wiki pkg`/2.1.0" \
  "https://wiki.adom.inc/api/v1/pages/<slug>/stars"   # {"count":N,"starred_by_me":bool}

---
name: wiki-scoring
description: >-
  The scoring / trending system on the Adom Wiki, the signals tracked to know
  whether a page is doing well (stars / high-fives, install counts, and a
  trending surface) and how an author legitimately earns them (great hero, strong
  README, working demo). Stars are live; install counts, high-fives, and a
  dedicated trending endpoint are still being surfaced. Read this when asked how a
  page is performing or how to make one trend. Trigger words: wiki scoring, wiki
  trending, high five, star a page, install count, is my page trending, page
  popularity, wiki metrics, how to trend, what's popular on the wiki, page score.
---

Parent skill: **adom-wiki-skillpack**

# Scoring & trending

The wiki tracks engagement signals so good pages surface, the equivalent of
stars + download counts driving a "trending" view. The intent is to capture
everything that indicates a page is valued; the surfacing is partly built.

These signals are the **ranking input to discovery** (a first-class wiki pillar ,
see **wiki-discovery**). Scoring answers "how valued is this page?"; discovery
answers "can it be found at all?" Relevance should surface a page; scoring should
break ties among relevant results, a great new page shouldn't be invisible just
because it has zero stars yet.

## Status

- **Stars: live.** `POST/DELETE /api/v1/pages/:slug/star` and
  `GET /api/v1/pages/:slug/stars` work (`→ {"count":N,"starred_by_me":bool}`).
- **High-fives / install counts / a dedicated trending endpoint: Partial /
  Planned.** These signals are intended but not yet exposed through the public API
 , page metadata doesn't surface install/high-five/score fields today, and
  `GET /api/v1/trending` returns 404. Treat trending rank as not-yet-queryable.

Don't report a numeric "score" or "trending rank" you can't read from the API.
Stars you can read and state; the rest, describe as intended, and re-probe before
claiming numbers.

## The signals (the model)

- **High-fives**, lightweight positive user feedback on a page.
- **Stars**, a user bookmarking/endorsing a page (live).
- **Install counts**, how many times the package was installed (the strongest
  signal of real use).
- **Activity**, commits, releases, discussions, recency.

These roll up into a **trending** surface so the wiki homepage and the
adom-screensaver billboards can promote what's hot.

## How to earn it (what moves the needle)

Scoring rewards the same things that make a page genuinely good, there's no trick
substitute:

- **A great hero** (see **wiki-hero**), it's what cards, the homepage, and the
  screensaver display; readable in one second.
- **A strong README with a working demo** (see **wiki-readme**), humans install
  what they can see working; install count is the heaviest signal.
- **Clear value + correct discovery triggers** so the right people find it.
- **Keep it alive**, releases, answered discussions, merged PRs.

So "how do I make this trend?" reduces to: make the page legitimately excellent
and easy to discover. The scoring system is designed to surface exactly that.

## Reading what's available now

```bash
curl -s -H "User-Agent: `adom-wiki pkg`/2.1.0" \
  "https://wiki.adom.inc/api/v1/pages/<slug>/stars"   # {"count":N,"starred_by_me":bool}
```

Update this skill as install-count / high-five / trending endpoints come online ,
re-probe and label them honestly.