agentleFS
Sign inStart free
adityareddy-devadityareddy-dev/deskstudio/skills/init/SKILL.md

init

Skill43 starsChanged 23 days agoMITView on GitHub

Set up Desk Studio in this project. Finds the brand in the project, writes .desk/DESIGN.md and .desk/project.json with the model tiers, and says what it found.

137 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • gaebalaiSkill

    codex-system

    PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".

    Also in 3 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 125 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create .desk/, .desk/out/, .desk/jobs/ in the project root if missing, and a .desk/.gitignore containing jobs/, events.jsonl, …

    line 9
  2. Very specific:

    If .desk/DESIGN.md is missing, follow ${CLAUDE_PLUGIN_ROOT}/skills/desk/procedures/brand-from-project.md.

    line 10
  3. Very specific:

    If .desk/project.json is missing, write the defaults from the end of ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md, with --quality applied if …

    line 11

“Common” is measured: kept by at least 6 in 10 of the 125 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Set up .desk/ for this project.

  1. Create .desk/, .desk/out/, .desk/jobs/ in the project root if missing, and a .desk/.gitignore containing jobs/, events.jsonl, dashboard.runtime.json.
  2. If .desk/DESIGN.md is missing, follow ${CLAUDE_PLUGIN_ROOT}/skills/desk/procedures/brand-from-project.md. If --brand gives a colour or a URL, use that instead of asking.
  3. If .desk/project.json is missing, write the defaults from the end of ${CLAUDE_PLUGIN_ROOT}/skills/desk/SKILL.md, with --quality applied if given.
  4. Tell the user in three lines: where the brand came from, the three tiers and their models, and that /desk:design <ask> is the next thing to type.

Arguments: $ARGUMENTS

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free