Skip to content
Back to search

lasuite-skills

MarketplaceWorks with Claude CodeGitHub

Skills used by LaSuite (DINUM) PMs.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/lslaroche--lasuite-skills/badge.svg)](/listings/lslaroche--lasuite-skills)

HTML

<a href="/listings/lslaroche--lasuite-skills"><img src="/api/listings/lslaroche--lasuite-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "lasuite-skills",
  3. "description": "Skills used by LaSuite (DINUM) PMs.",
  4. "owner": {
  5. "name": "Louis Laroche"
  6. },
  7. "plugins": [
  8. {
  9. "name": "lasuite",
  10. "source": "./plugins/lasuite",
  11. "description": "Weekly OBEYA post, LaSuite design system and brand, functional QA, GitHub issues, product framing, PostHog insights."
  12. }
  13. ]
  14. }
README.md · README · 91 lines
  1. # lasuite-skills
  2. Claude skills used and shared by the LaSuite team (DINUM), distributed as a plugin (`lasuite`). Anyone can install it, and every change pushed here reaches all synced accounts.
  3. This repo is public. No personal content, no internal ids (PostHog projects, dashboards) and no real usage numbers here: everything written must be useful to the whole team and safe to publish.
  4. ## Tree
  5. ```
  6. .claude-plugin/marketplace.json Claude plugin catalog (must stay at the root)
  7. plugins/ the plugins, one folder per plugin
  8. README.md
  9. LICENSE
  10. ```
  11. Anything added later (prompts, notes, evals, experiments) lives in its own folders at the root, next to `plugins/`. Claude only reads `.claude-plugin/marketplace.json` and the paths declared in it; the rest of the repo is invisible to it.
  12. ## The plugin catalog
  13. `.claude-plugin/marketplace.json` is a *plugin marketplace*: a catalog that Claude accounts add once, and that serves them the plugins listed in it along with their updates.
  14. | Plugin | Skills |
  15. |---|---|
  16. | `lasuite` | `obeya`, `ui-kit`, `qa`, `github-issue`, `product-framing`, `posthog-insight` |
  17. The catalog name (`lasuite-skills`, defined in `marketplace.json`) is the suffix after `@` at install time.
  18. ### Requirements per skill
  19. The skills check these accesses at startup and ask the user to connect them when missing.
  20. | Skill | Required access |
  21. |---|---|
  22. | `github-issue` | `gh` logged in, local copy of the target repo, PostHog MCP |
  23. | `qa` | Docs MCP (spec), Figma MCP (design), `gh` logged in (CI), local copy of the repo |
  24. | `obeya` | PostHog MCP when the product sheet has a tracked stat |
  25. | `ui-kit` | access to the `suitenumerique/ui-kit` repo: installed package, local clone or `gh` logged in |
  26. | `product-framing` | Docs MCP or `gh` logged in when the material is a link |
  27. | `posthog-insight` | PostHog MCP (read-only), access to the product's PostHog project |
  28. ### Product sheets (local)
  29. `obeya` and `posthog-insight` read a product sheet that stays on each PM's computer, never in this repo: `~/.lasuite-skills/products/<product>.md`. It holds the PostHog project and dashboards, and for the obeya the tracked stat, its SQL query and the start of its history. The template is `plugins/lasuite/skills/obeya/references/product-sheet-template.md`.
  30. Without a sheet, the skill asks the PM for the information, checks it in PostHog and offers to write the sheet. To share a sheet with another PM, send the file directly.
  31. ## Writing conventions
  32. - Skills are written in English.
  33. - Each skill has a "Language" section stating the language of its output: always English for anything posted on GitHub, French for Tchap posts, the user's choice for local documents.
  34. - Facts that change with a dependency (components, tokens, versions) are read from their source repo, never hardcoded in a skill.
  35. - Examples use fictional first names and numbers.
  36. ## Add this catalog to a Claude account
  37. In claude.ai or the desktop app: **Customize > Plugins > Add > Add marketplace**, then enter `lslaroche/lasuite-skills`.
  38. Then install `lasuite` from the list, and turn on **Sync automatically** on the catalog to receive updates (otherwise **Check for updates**).
  39. From the command line (Claude Code):
  40. ```bash
  41. claude plugin marketplace add lslaroche/lasuite-skills
  42. claude plugin install lasuite@lasuite-skills
  43. ```
  44. ## Edit a skill
  45. 1. Edit the relevant `SKILL.md` under `plugins/<plugin>/skills/<skill>/`.
  46. 2. Bump `version` in `plugins/<plugin>/.claude-plugin/plugin.json`.
  47. 3. Open a pull request.
  48. 4. Once merged, accounts with automatic sync get the new version.
  49. ## Add a plugin
  50. 1. Create `plugins/<name>/.claude-plugin/plugin.json` with at least `name` (kebab-case) and `version`.
  51. 2. Add its skills under `plugins/<name>/skills/<skill>/SKILL.md`.
  52. 3. Add an entry to the `plugins` array of `marketplace.json`, with `name` and `source`.
  53. Two rules that break the install if missed: a relative `source` must never contain `..`, and the `name` of a catalog entry must match the `name` of the corresponding `plugin.json`.
  54. ## Validate before pushing
  55. ```bash
  56. claude plugin validate ./plugins/lasuite
  57. claude plugin validate .
  58. ```
  59. ## License
  60. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.