agentsclimarketplace
Sign in

Tle developer flagos

Skill flagos-ai/skills/skills/tle-developer-flagos

Self-contained orchestration skill for writing high-performance TLE kernels and shipping TLE feature changes with reproducible validation. Use when the user wants to write/optimize TLE kernels, implement TLE API/verifier/lowering features, or debug TLE correctness/performance issues. Trigger on phrases like "write a TLE kernel", "optimize TLE operator", and "debug TLE local_ptr".From its SKILL.md

Install
npx -y skills add flagos-ai/skills --skill tle-developer-flagos

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, as published. Nobody here has run it

<!-- Copyright 2026 FlagOS Contributors Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -->

TLE Developer

Mission

Use this skill to execute TLE work end-to-end: intake -> implementation -> validation -> artifacts -> merge decision.

Scope

Use for:

  1. Writing or optimizing TLE kernels.
  2. Implementing TLE API/verifier/lowering/pipeline features.
  3. Debugging correctness, performance, and regression issues.

Self-Contained Policy

  1. Do not rely on documentation outside this skill folder.
  2. Put all detailed guidance in references/.
  3. Keep this file as orchestration-only (no duplicated deep details).

Required Input

Start every task with:

Goal:
Non-goal:
Acceptance:
Impact scope (optional):

Mandatory Read Order

  1. references/tle-sources.md
  2. references/workflow-templates.md

Operating Contract

  1. Treat references/tle-sources.md as the technical source of truth for:
    • quickstart,
    • current TLE semantics contract,
    • kernel patterns,
    • feature-development file map,
    • debug/perf procedures.
  2. Treat references/workflow-templates.md as the source of truth for:
    • intake,
    • validation matrix,
    • performance record,
    • fix summary,
    • lessons entry,
    • merge package.

Non-Negotiable Guardrails

  1. Never assume a specific python environment name.
  2. Never assume a fixed build script name.
  3. If native Triton files are modified, use marker blocks: // begin flagtree tle and // end flagtree tle.
  4. Do not add marker blocks inside third_party/tle.

Required Outputs Per Task

  1. Validation commands and outcomes.
  2. Fix Summary (when fixing bugs or regressions).
  3. Lessons Entry (for fixes and optimization work).
  4. Merge Decision Package (changed layers, risks, follow-ups).

Completion Checklist

  1. Acceptance criteria mapped to tests.
  2. Changes validated with reproducible commands.
  3. Artifacts filled from templates.
  4. Residual risks explicitly stated.

References

  1. references/tle-sources.md
  2. references/workflow-templates.md

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.