SKILLEMALL.ai
GitHub ↗ RU Sign in

BB ogp-project

Tool-agnostic project collaboration for AI assistants. Users keep their own tools (Linear, Jira, Obsidian, GitHub, iCloud, local files — anything). This skill makes agents aware of what each collaborator's agent knows and where it lives, so agents can query each other proactively rather than making the human relay information. Supports project creation with context interviews, freeform activity logging, proactive pre-task peer checks, and cross-peer summarization.

ClawHub Agent Skills author: latentgenius v0.6.0 MIT-0 2 files body ≈ 4 512 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 70/100 · Nearly there — weak spots: when it triggers, running it twice

GeneratorGitHubObsidianJiraAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
54
Run on models
none yet
Process rating
B
70/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

    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: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • error name-missing SKILL.md: frontmatter has no `name`
    • note frontmatter-key unknown frontmatter key "skill_name"
    • note frontmatter-key unknown frontmatter key "trigger"
    • note frontmatter-key unknown frontmatter key "requires"

    Process rating: all ten parameters 70/100

    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 8 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4512 tokens
    • 100Steps. 66 steps
    • 100Failures and branches. 6 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Progress reporting. Reports progress
    • low 13 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (4 tags): a typed call is more reliable

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 468: enough signal without eating the budget
    • +4Structure: 42 headings
    • +3Step-by-step instructions: 66 items
    • +3Output format is stated explicitly
    • +4Has examples (23 code blocks)

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

    External checks

    ClawHub: suspicious
    This skill is a legitimate project-collaboration helper, but it can persist project details and automatically share work context with approved peer agents more broadly than users may expect.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026