The Store

Discover brings collections, categories, theme previews and people together on desktop, the phone and the web. Open a collection to explore skills for a task, or browse a category to see more. Collections use published catalog entries, ordered by installs on skills.sh; they are not security reviews.

Every account has a profile, with a random username to start. It is private until you turn on Make my profile public in your account, under Profile (the account menu’s Your profile takes you there; in the desktop app it is in Settings, Account). Until then others see only your username and that the profile is private; your name, photo and token activity stay hidden. Change the username whenever you like: it is your page, deska.dev/@username, which you can share with the Share button on it once it is public. Add a display name, a short bio and an optional HTTPS website. Your published bundles, panels and themes appear together. Your installed items and drafts never appear on your profile.

Your photo is the round picture at the top of Edit profile: press it, or Add photo, and choose one (JPEG, PNG, WebP or GIF, up to 15 MB). It goes up at once, cropped to a square, without camera details such as where it was taken. Until you choose one, your profile shows the photo of the account you sign in with (Google, GitHub or Apple), if it has one. Remove photo takes it off and shows your account’s default picture, the same one as in your account menu. Photos are served by deska.dev itself, so a visitor’s browser never asks anyone else for them.

On the web, the Store is under Explore in the site menu. A row at the top of its pages moves between Discover, Skills, Bundles, Panels, Themes and People. People is a ranking: everyone who publishes in the Store or shares their token activity, ordered by what their tokens of the last 12 months are worth at API prices. Each row shows the person’s position, photo or default picture, name and username, the marks of the model makers they use (Claude, OpenAI), and on the right the value, exact to the dollar, over their tokens, with a thin bar against first place. Someone who does not share activity shows what they publish, or their bio, instead. Top is the ranking; New, beside the search, lists the newest profiles first. Signed in, your own row is pinned above the list with You and your position; if your profile is private it says so, with Make it public. A search there finds profiles by name, username or bio, closest first, without positions. The desktop app and the phone show the same ranking. A search in the Store finds people too, first, under People, with See all people for the rest. In the desktop app People has its own row in the Store’s sidebar, and on the phone it is near the end of Discover; in both, a search in the Store lists people first as well.

Every bundle, theme and panel names who made it, with their photo or default picture. When the maker’s Deska profile is public, their name opens it; the rest of the row or card still opens the item. Deska’s own themes and bundles, and the panels included in Deska, carry the Deska mark. Imported skills still credit their original GitHub maker; a Deska profile does not claim someone else’s repository. Edit profile, on your own page, opens that account section, where you change your username, name, bio, website, accounts and photo. If you change your username, your old link stops working.

Your profile can also show your accounts on X, Instagram, TikTok and GitHub, under your bio: each network’s mark and your @username, linked to your page there. Add them in Edit profile, under Your accounts: type the username, or paste your profile’s address and Deska keeps only the username. Deska saves nothing but the username and builds each link on the network’s own site, so a profile can never send someone elsewhere under a network’s name. A GitHub username there does not make you the maker of skills imported from GitHub.

Your profile also shows your token activity: a year of squares, one a day, deeper as your Claude Code, Codex, OpenCode and Antigravity agents used more tokens, sent by Deska on your computers. Cursor keeps no token counts on your computer, so it is not counted. Above the squares, in large type, is what those tokens are worth at API prices over the last 12 months, exact to the dollar (for example $212,431). That is a value, not what you paid: most people run these agents on a subscription. It prices every token at its maker’s API list price for its model, cached input included, while the squares count only new input and output.

Deska counts from the logs the agents keep, and Claude Code deletes its own after 30 days unless you change its cleanupPeriodDays. So the graph draws a line at the first day it counted in full, about 30 days before Deska first read your computer, and the note under it says Counted in full since that day. Before the line, a day shows only what the agents had not deleted yet: an empty one is drawn fainter than a day without work and says Not measured, and one with tokens says Partly measured. After it, Deska keeps every day it read, even when the agent deletes the log, as long as Deska opens at least once within that 30 days. If it does not, the line moves up.

Point at a square to see its day: the date, its value and tokens, then the models used that day, up to four with their own value and tokens, and how many more. On a touch screen, tap the square; tap it again to close it. With a keyboard, Tab to the graph and move with the arrow keys, a day with up and down and a week with left and right; Escape hides the day, and a screen reader reads each one. Under the graph, By model lists the year’s models, most valuable first, each with its maker’s logo (Claude or OpenAI), its value, its tokens and a bar of its share of the year’s value. The first six show, and the button under them shows the rest and hides them again. A value under a dollar shows its cents, like $0.42, and one under a cent reads <$0.01, never $0. A model Deska has no price for yet says No price; its tokens still count. The graph, its value and the models are public unless you turn off Show my token activity on my profile in Edit profile, which hides all three; you still see them, marked private.

The Store opens from the top right of the desktop app, and from the Home header in the phone app. It has shelves: Skills, Bundles, Panels and Themes. You can search each shelf and sort it, and each item has its own page with what it is, who made it and where it comes from.

The same shelves are on the web at deska.dev/skills, deska.dev/skills/bundles, deska.dev/panels and deska.dev/themes. Open in Deska on those pages opens the item in the app’s Store. It never installs anything by itself: you choose what, where and for which agents in the app.

On the web, deska.dev/skills opens on the Store’s front page: featured bundles, the most installed and trending skills as numbered lists, the categories (Design and frontend, Testing and quality, Writing and docs and more) and the makers with official skills. Every category and every maker has its own page, and one search covers skills, bundles, panels and themes at once. See all skills lists every skill sorted by Popular, Top or New.

A skill teaches your coding agents something new: a folder with a SKILL.md file and, sometimes, scripts. Claude Code, Codex, OpenCode, Cursor and Antigravity all read skills from their own skills folders.

Deska lists skills; it does not host them. Every listing points at a folder in its author’s GitHub repository, read at a commit you can see on its page, along with its license (or No license), how many files it has and whether any of them are scripts. A skill with scripts says This skill includes scripts your agent can run, and its Files list marks which ones.

When the repository’s license allows copying (MIT, Apache 2.0, BSD, ISC, MPL, CC0, the Unlicense or CC BY), the skill’s page shows its SKILL.md under Overview, as text: nothing in it runs on the page, and its links open in a new tab. Otherwise the page says so and links to the file on GitHub.

Install counts from skills.sh are shown as theirs, for example 1.3M installs on skills.sh, with a link. Deska’s own upvotes are counted separately and never added to them.

skills.sh also shows security audits that partners run on each skill (today Gen Agent Trust Hub, Socket and Snyk). When one of them fails a skill, Deska says so: the skill’s rows read Fails an audit, its page links to the audit, and a bundle that holds it says how many of its skills fail one. Those verdicts are theirs, about the version they scanned, and a passing audit is not a promise that a skill is safe.

Press Install on a skill, then choose:

• The computer. This computer, a Deska Cloud box or another of your computers. A sleeping box wakes up first. A computer that needs a newer Deska says so.
• Where. Everywhere on this computer, for every project, or This project, which writes the skill into the project’s folder (for example .agents/skills and skills-lock.json). Deska never commits those files; Source Control shows them.
• The agents. Every agent installed on that computer is selected; turn off the ones you do not want.

Deska runs the open skills command line at a fixed version and shows its progress. If it fails, the Store shows its last lines. A skill installed everywhere is also linked into every separate agent account on that computer, including accounts you add later. Installed lists what each computer has, including skills you installed without Deska, with Update and Remove. On this computer it also lists each open project’s own skills, under the project’s name.

On your own computer the command line needs Node.js; the Store links to it if it is missing. Deska Cloud boxes already have it.

A bundle is a named list of up to 30 skills from the Store, installed in one press: say, the five skills someone used on a stream. Any signed-in account can make one, in the app or on the Store section of your account page, and share its link at once. Bundles are saved to your Deska account, not to one computer. In the app, the skills already on your computers that the Store lists are offered first.

A new bundle works by its link but is not on the Bundles shelf. Listing it puts it there at once. When Deska reviews bundles first, the button asks for a review instead and Deska staff decide; changing a listed bundle then sends it back to review. A bundle never copies a skill: installing it installs what each repository holds at that moment.

Every listed bundle is at deska.dev/skills/bundles, sorted by Top or New, with a search.

A theme is a look for Deska someone shared: one of Deska’s base themes, an accent color and a canvas background (a built-in wallpaper, a gradient, a solid color, a moving background, or their own image or video). It is data, never code: it cannot run anything, hide a control or reach the internet. Browse them in the app’s Store or at deska.dev/themes, filtered to dark or light.

In the app, a theme’s page has Apply, which sets your theme, accent and canvas background on that computer, and Back to my look, which puts back what you had. A background image or video is downloaded once. The phone shows themes and takes votes; apply them from a computer.

To share yours, use Share my look in the Store. Images up to 5 MB and MP4 or WebM videos up to 25 MB travel with it. Your look is listed as soon as you share it, unless Deska is reviewing themes first, which the page says before you send. Your account page shows where yours stand under My themes, where you can also delete them, and Deska can take down any listing.

Signed in, you can upvote a skill, a bundle, a community panel or a theme once, and take the vote back. Top sorts a shelf by these votes, Popular by installs (for themes, how many people applied them) and New by when the item arrived. Vote counts are public; who voted is not.

Missing a skill? Suggest its GitHub repository from the Store section of your account page: Deska reads every SKILL.md in it and lists its skills right away, or, when Deska reviews suggestions first, staff read it before it is added. Something wrong with a listing? Every skill, bundle and theme page has a Report link. Deska removes a listing whose author asks for it to be taken down.

Browsing the Store and voting talk to deska.dev, which keeps your votes and your bundles. Installing a skill makes the chosen computer download the skills command line from npm (Deska Cloud boxes have it already) and the skill from its repository. Deska turns off the command line’s own install reporting, so skills.sh receives nothing from Deska.

Community panels follow their own rules: see Community panels.