DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to set up an agent workspace for Triton-Ascend work with Triton Ascend Agent Dev Kit

Build or download the kit and unpack it into the folder your AI agent works in.

Who it is forA developer on an Ascend NPU machine who wants an AI agent to help with Triton-Ascend kernel work and needs the kit in place first.

The problemThe agent has no project rules or Triton-Ascend references for this work, so its suggestions may be generic.

The outcomeThe agent's working folder holds AGENTS.md, the guide index, the development references, and the skills folder from this kit.

What you need first

  • A shell to run the build script, or access to the repo's Releases page to download an archive
  • An AI agent that can read files in a working folder
  • Access to an Ascend NPU environment for running the kernels the agent produces
  • Familiarity with Triton-Ascend, since the README points to its official docs for reference

Steps

  1. Run build-workspace-agent-specific-kit.sh from the repo, or download the archive for your agent from the Releases page instead.
  2. Take the archive for your agent from the dist/ folder.
  3. Unpack the archive into the agent's working folder.
  4. Open AGENTS.md and triton-ascend-dev-doc.md so the agent knows the project rules and how to load the guides.

Prompt for your agent

In the triton-ascend-agent-dev-kit workspace at <working-folder>, list AGENTS.md, triton-ascend-dev-doc.md, the triton-ascend-dev-doc/ folder, and the skills/ folder. Expected output: those four items with the number of entries in skills/. Verify that skills/ contains 24 task-specific skills, as the README states.

Caveat. The README warns that Triton-Ascend and the NPU change often, so guidance from the kit may not fit your exact environment.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page