Cometchat Android V6 Production
cometchat/cometchat-skills
Ship a CometChat Android v6 app safely — server-minted auth tokens instead of the dev Auth Key, keeping credentials out of the APK, release-build and R8/ProGuard checks, user provisioning…
Every public Google Play surface in one Go binary Trigger phrases: top grossing games on google play, google play app details for, track this app's rank over time, what changed on this play store…
$ npx skills add mvanhorn/printing-press-library --skill pp-google-play -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-play --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-google-play .claude/skills/pp-google-play && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pp-google-play" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-play into .claude/skills/pp-google-play/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-play", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-playType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-play -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-play --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-google-play .agents/skills/pp-google-play && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-google-play" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-play into .agents/skills/pp-google-play/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-play", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-play -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-play --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-google-play .cursor/skills/pp-google-play && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pp-google-play" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-play into .cursor/skills/pp-google-play/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-play", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mvanhorn/printing-press-library.git --path cli-skills/pp-google-play--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-play -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-play --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-google-play .gemini/skills/pp-google-play && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pp-google-play" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-play into .gemini/skills/pp-google-play/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-play", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mvanhorn/printing-press-library pp-google-playInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mvanhorn/printing-press-library --skill pp-google-play -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-google-play .github/skills/pp-google-play && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pp-google-play" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-play into .github/skills/pp-google-play/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-play", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-play -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-play --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-google-play .opencode/skills/pp-google-play && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pp-google-play" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-play into .opencode/skills/pp-google-play/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-play", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pp-google-playEvery public Google Play surface in one Go binary Trigger phrases: top grossing games on google play, google play app details for, track this app's rank over time, what changed on this play store…
Pp Google Play is an agent skill from mvanhorn/printing-press-library. Every public Google Play surface in one Go binary Trigger phrases: top grossing games on google play, google play app details for, track this app's rank over time, what changed on this play store listing, reviews for this android app, use google-play, run google-play.
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Mobile, covering App store release and Android development. It works with Android. The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 76de244. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudenpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Google Play loads about 3.4k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 1,417 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mvanhorn/printing-press-library at commit 76de244, republished under its Apache-2.0 licence (© mvanhorn). 1,417 words, ~3,399 tokens.
.claude/skills/pp-google-play/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/marketing/google-play/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
This skill drives the google-play-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install google-play --cli-onlygoogle-play-pp-cli --version$PATH for the agent/runtime that will invoke this skill.If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:
go install github.com/mvanhorn/printing-press-library/library/marketing/google-play/cmd/google-play-pp-cli@latestIf --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.
Pull app details, top charts, search, reviews, similar apps, developer portfolios, permissions, and data safety from the public Play Store with no API key. Then go further than any existing scraper: snapshot charts and listings into a local database so 'movers', 'rank-history', 'keyword-history', and 'watch-listing' can answer week-over-week questions Google never exposes and commercial tools paywall.
Use this CLI when you need structured, scriptable Google Play Store data without an API key: profiling an app and its competitive set, tracking chart and keyword rank over time, detecting listing changes, or mining reviews. It is built for mobile game and app market intelligence, ASO research, and AI agents that need clean JSON and a typed rate-limit signal.
Do not use this CLI for:
These capabilities aren't available in any other tool for this API.
movers — See which games climbed, dropped, entered, or fell off a Play chart between two snapshots.
Reach for this when an agent needs week-over-week rank movement that Play never exposes and Sensor Tower paywalls.
google-play-pp-cli movers --collection TOP_GROSSING --category GAME_PUZZLE --country us --agentrank-history — Show one app's rank trajectory over time within a chart, including first-seen, peak, and last-seen rank.
Pick this when you need the trend line for a single title, not the whole chart.
google-play-pp-cli rank-history com.dreamgames.royalkingdom --collection TOP_GROSSING --category GAME --country us --agentwatch-listing — Diff the two latest snapshots of a listing to surface what changed: title, icon, version, IAP range, ads flag, price, screenshots.
Use this to catch a competitor's monetization or positioning shift the moment it ships, instead of eyeballing screenshots.
google-play-pp-cli watch-listing com.yalla.yallagames --agentkeyword-rank — Run a live store search for a term and record where a target app ranks, persisting the data point for trend analysis.
Reach for this to log today's keyword position so tomorrow's metadata change can be measured.
google-play-pp-cli keyword-rank "merge puzzle" --country us --app com.yalla.yallagames --agentkeyword-history — Show the rank-over-time series for a term, app, and country from captured keyword snapshots.
Use this to prove whether a listing change actually moved a keyword over time.
google-play-pp-cli keyword-history "merge puzzle" --country us --app com.yalla.yallagames --agentreview-digest — Aggregate synced reviews into star and per-version histograms, developer reply rate, and complaint-term frequency, with no NLP.
Pick this for mechanical post-update sentiment stats; pipe the output to an LLM if you want prose.
google-play-pp-cli review-digest com.yalla.yallagames --agentcompare — Fetch details for several apps and lay their key fields side by side in one table.
Use this to benchmark a title against its competitive set in a single call.
google-play-pp-cli compare com.yalla.yallagames com.dreamgames.royalkingdom --agent --select items.appId,items.score,items.installs,items.offersIAPThis CLI was generated with browser-observed traffic context.
categories — Enumerate Google Play app/game categories from the public store
google-play-pp-cli categories — List Google Play category slugs (GAME_ACTION, GAME_PUZZLE, ...) scraped from the store navWhen you know what you want to do but not which command does it, ask the CLI directly:
google-play-pp-cli which "<capability in your own words>"which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.
google-play-pp-cli app com.dreamgames.royalkingdom --agent --select appId,title,developer,score,realInstalls,offersIAP,containsAdsNarrow a verbose detail payload to the fields an agent actually needs.
google-play-pp-cli movers --collection TOP_GROSSING --category GAME --country us --agentDiff the two most recent chart snapshots to see who climbed and who fell off.
google-play-pp-cli keyword-rank "merge puzzle" --country us --app com.yalla.yallagames && google-play-pp-cli keyword-history "merge puzzle" --country us --app com.yalla.yallagames --agentCapture today's rank, then read the trend series back.
google-play-pp-cli reviews com.dreamgames.royalkingdom --limit 100 --agent --select userName,score,text,atReviews return tens of KB; --select with --agent keeps only the fields you parse.
No authentication. Every command reads the public Play Store anonymously. The CLI throttles to about two requests per second by default (set with --rate-limit) and backs off on rate-limit responses, including the PlayGatewayError that Google returns inside an HTTP 200 body.
Run google-play-pp-cli doctor to verify setup.
Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.
Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
google-play-pp-cli categories --agent --select id,name,statusPreviewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests
Commands that read from the local store or the API wrap output in a provenance envelope:
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.
When you (or the agent) notice something off about this CLI, record it:
google-play-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
google-play-pp-cli feedback --stdin < notes.txt
google-play-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.local/share/google-play-pp-cli/feedback.jsonl. They are never POSTed unless GOOGLE_PLAY_FEEDBACK_ENDPOINT is set AND either --send is passed or GOOGLE_PLAY_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
google-play-pp-cli profile save briefing --json
google-play-pp-cli --profile briefing categories
google-play-pp-cli profile list --json
google-play-pp-cli profile show briefing
google-play-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show google-play-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/marketing/google-play/cmd/google-play-pp-mcp@latestclaude mcp add google-play-pp-mcp -- google-play-pp-mcpclaude mcp listwhich google-play-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:google-play-pp-cli <command> [subcommand] [args] --agentgoogle-play-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-google-play of mvanhorn/printing-press-library.
Open the folder on GitHubat commit 76de244
Pp Google Play next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pp Google Play this skillmvanhorn/printing-press-library | 2.1k | — | ~3.4k | Automated safety check: Notes | Apache-2.0 | |
| Cometchat Android V6 Productioncometchat/cometchat-skills | 131 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Mobile App Builderrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Android Readme Screenshot Studiopermissionlesstech/bitchat-android | 7.8k | — | ~3k | Automated safety check: Pass | GPL-3.0 | |
| Generating Baseline ProfilesrosuH/EasyWatermark | 1.9k | 1 repos | ~5k | Automated safety check: Pass | Apache-2.0 | |
| Ipaship Auditatharvnaik1/ipaship-audit | 108 | — | ~1.5k | Automated safety check: Notes | MIT |
cometchat/cometchat-skills
Ship a CometChat Android v6 app safely — server-minted auth tokens instead of the dev Auth Key, keeping credentials out of the APK, release-build and R8/ProGuard checks, user provisioning…
revfactory/harness-100
Full mobile app development pipeline. An agent skill from revfactory/harness-100.
permissionlesstech/bitchat-android
Create or refresh polished, high-resolution screenshots of the Bitchat Android app for README and repository showcase use.
rosuH/EasyWatermark
A skill your agent uses to generate and measure Jetpack Compose Baseline Profiles end-to-end with the AGP 8.2+ Baseline Profile Generator module and the Macrobenchmark harness.
atharvnaik1/ipaship-audit
A skill your agent uses when auditing iOS/Android app submissions for compliance with Apple App Store Review Guidelines or Google Play Developer Policies.
timusus/Shuttle2
Deploy the Android app to the Play Store via GitHub Actions.
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Works with
Categories
Every public Google Play surface in one Go binary Trigger phrases: top grossing games on google play, google play app details for, track this app's rank over time, what changed on this play store…. Pp Google Play is an agent skill from mvanhorn/printing-press-library. Every public Google Play surface in one Go binary Trigger phrases: top grossing games on google play, google play app details for, track this app's rank over time, what changed on this play store listing, reviews for this android app, use google-play, run google-play.
Pp Google Play fits situations like: phrases: top grossing games on google play; google play app details for; track this apps rank over time; what changed on this play store listing.
Run `npx skills add mvanhorn/printing-press-library --skill pp-google-play -a claude-code`. Or copy the skill folder (cli-skills/pp-google-play in mvanhorn/printing-press-library) into .claude/skills/pp-google-play in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-google-play -a codex`. Or copy the skill folder (cli-skills/pp-google-play in mvanhorn/printing-press-library) into .agents/skills/pp-google-play in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-google-play -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-google-play, .gemini/skills/pp-google-play, .github/skills/pp-google-play and .opencode/skills/pp-google-play in your project.
Going by SKILL.md and its folder, Pp Google Play needs the command-line tools its instructions call (go, claude and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Google Play is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Google Play: Cometchat Android V6 Production (cometchat/cometchat-skills, 131 stars), Mobile App Builder (revfactory/harness-100, 1.3k stars), Android Readme Screenshot Studio (permissionlesstech/bitchat-android, 7.8k stars) and Generating Baseline Profiles (rosuH/EasyWatermark, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.