SkillAgentSearch skills...

mechsys

Use when a task mentions MechSys, tdem, tlbmdem, DEM/Particle/Voronoi optimization, CUDA DEM tests, LBM-DEM, or the MechSys simulation library in this workspace.

Install / Use

npx skills add Axtal/mechsys

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

70/100

Supported Platforms

Universal

Tags

Our assessment of mechsys

mechsys scores 70/100 on our quality scale, 1083rd of 1,182 Content & Media skills we index.

Its SKILL.md is 5.0 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so mechsys is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

mechsys compared with similar skills

All 4 of these similar skills score higher than mechsys; compare them before choosing.

SkillScoreStarsUpdatedFormat
mechsys (this skill)by Axtal7003d agoSKILL.md
siyuanby siyuan-note10046.9ktodayMCP Server
algorithmic-artby anthropics100177.9k34d agoSKILL.md
pptxby anthropics100177.9k34d agoSKILL.md
designby nextlevelbuilder100137.2k11d agoSKILL.md

Frequently asked questions

How do I install mechsys?
Run npx skills add Axtal/mechsys. The install tabs above show the steps for each supported agent.
Which AI agents does mechsys work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is mechsys safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is mechsys still maintained?
The repository was last updated 3 days ago, so mechsys is actively maintained.

name: mechsys description: Use when a task mentions MechSys, tdem, tlbmdem, DEM/Particle/Voronoi optimization, CUDA DEM tests, LBM-DEM, or the MechSys simulation library in this workspace. whenToUse: Any request to inspect, build, benchmark, debug, optimize, or document this MechSys checkout, especially its CPU DEM, CUDA DEM, LBM-DEM, or FLBM paths.

MechSys

This is the visible, downloadable copy of the MechSys skill. DSH discovers .agents/skills/mechsys/SKILL.md; keep the two files in sync.

This is the project-local skill for the MechSys checkout. It is discovered automatically from .agents/skills/mechsys; do not install a separate plugin just to provide this static guidance.

The authoritative context is:

  1. AGENTS.md — automatic, concise agent rules.
  2. MECHSYS_HANDBOOK.md — architecture, build/run commands, exactness procedure, benchmarks, and known traps.
  3. MEMORY.md — distilled experience and a short verification checklist.
  4. The optimization reports:
    • CPU_DEM_OPTIMIZATION_CHANGES.md
    • CUDA_OPTIMIZATION_CHANGES.md
    • REDUCED_TEST_CU_03_PERFORMANCE.md

Read the relevant documents before making substantive changes, and update them when a durable lesson or corrected benchmark is learned.

Non-negotiable rules

  • Do not assume a given checkout or HEAD contains the optimized state. Check git status, the reports, and compare against a clean baseline created from the chosen commit.
  • CPU DEM exactness is checked at Nproc=1 by comparing HDF5 datasets, not whole-file MD5. Expect neq [] and matching printed energies.
  • Preserve candidate-list order and the original Distance arithmetic in the contact path. Do not sort the lists.
  • The CPU Verlet cutoff is Rsum + 4.0*ContactDispGlobal(). Do not lower it without a new safe derivation and an exact comparison.
  • Broadphase bounds must be conservative. If in doubt, remove a rejection rather than risk a missed contact.
  • CUDA test_cu_03/04 use atomicAdd; the baseline is non-deterministic. Do not claim bitwise equality for those GPU runs. Nthread=512 fails for the current large test; tested range is up to 384.
  • Keep the separate pTranslate + pRotate fallback. Making fused movement unconditional broke test_cu_04.
  • The outer solve loop owns Time/iter; publish them to CUDA with SetClock. Do not add independent clock increments in DEM or LBM substeps.
  • After changing lib/dem/*, build at least one CPU target, one CUDA target, and the relevant LBM-DEM target.

Rotation caches

Particle owns wrot = Rotation(w,Q) and Qc = Conjugate(Q). They are refreshed by CalcProps, InitializeVelocity, Rotate, UpdateContacts, and after a user Setup callback.

  • CUDA UploadParticle copies the host caches; it does not recompute them.
  • CUDA DnloadParticle copies the device caches back.
  • The built-in device movement kernels refresh the device caches after changing Q/w.
  • A custom GPU movement/rotation kernel that changes Q/w must refresh DPar[].wrot/DPar[].Qc itself.
  • Host code that assigns Q/w directly and bypasses the normal paths must call Particle::UpdateRotCache() before using the caches.

Build and run

From the repository root:

cd tdem
make -j8 test_periodic
make -j8 test_cu_01 test_cu_02 test_cu_03 test_cu_04
./test_periodic ../benchmarks/cpu_voronoi/tper_small 8

cd ../tlbmdem
make -j8 tlbmdem01 tlbmdem02
make -j8 tlbmdem_cu_01

test_periodic takes a FileKey prefix (the .inp suffix is appended). test_cu_03 takes Nproc, Verlet distance, and threads per block: ./test_cu_03 1 0.05 128. Full LBM-DEM and CUDA tests are long; use a temporary reduced copy for smoke tests and do not modify the checked-in test just to shorten it.

For one-off cases, use the configured standalone compiler: ./mechsyscc case.cu from the repository root (or the equivalent mechsyscc in the current installation).

FLBM / GPU fluid cases

  • lib/flbm/Domain.h is the fluid LBM; lib/flbm/lbm.cuh holds the CUDA kernels. Use D2Q9 with iVec3_t(nx,ny,1) for a 2-D GPU run.
  • The GPU streaming kernel resets BForce every step. A constant body force must be written back to dom.pBForce on the device in the Setup callback before collision; setting the host array once is not enough.
  • dom.Nthread controls the CUDA block size. The Nproc argument of Domain::Solve affects host packing/transfers on the GPU path.
  • CPU and GPU body-force conventions differ: CPU StreamSC adds 0.5*dt*BForce to the reported velocity, while the GPU fused kernel returns the raw second moment. The raw GPU moment carries a -0.5*nu*phi bias in permeability; use u_physical = u_raw + 0.5*dt*fx*phi.
  • Keep one-off FLBM cases outside the checkout; do not add them to tflbm/ unless they belong in the library test suite.

Reporting

Report measured wall times, separate solve time from total wall time, and explicitly distinguish what compiled, what ran, what matched a baseline, and what was faster. If a verification was not done, say so.

Related Skills

View on GitHub
GitHub Stars0
CategoryContent
Updated3d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low