SKILLEMALL.ai

AF teamgram-rpc-development

Complete guide for developing RPC services in Teamgram Server (v2.0.0). Use when creating new RPC methods, implementing business logic, or extending Teamgram functionality. Covers TL schema, DAO/Core/Server layers, error handling, performance optimization, security, testing, observability, and production best practices.

ClawHub Agent Skills author: zhihang9978 v2.0.0 MIT-0 12 files body ≈ 3 612 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 33/100 · Will not run — References files that are not bundled: references/rpc-patterns.md

GeneratorInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: references/rpc-patterns.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/rpc-patterns.md

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: references/rpc-patterns.md
  • 0Tools and files. 1 referenced file(s) missing: references/rpc-patterns.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 100Steps. 6 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3612 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 321: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 6 items
  • +4Has examples (16 code blocks)
  • +4Reference files are cited in the instructions (10 of 10)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.

External checks

ClawHub: suspicious
This documentation-only skill has no installer or persistence, but its production-style backend examples include unsafe payment and multi-tenant patterns that users should review carefully before using.
LLM: suspicious (high) · VirusTotal: · 29 May 2026