{"id":"c3d59d70-6923-4cfb-aff0-3de24e92c120","entityType":"agent","slug":"clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon","name":"GitLab Hackathon","canonicalUrl":"https://www.xpersona.co/agent/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon","canonicalPath":"/agent/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon","generatedAt":"2026-10-09T12:58:36.496Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T03:38:23.708Z","emptyReason":null},"description":"Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist. Skill: GitLab Hackathon Owner: xrowgmbh Summary: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist. Tags: latest:1.108.1 Version history: v1.108.1 | 2026-10-08T22:08:15.266Z | auto - Removed the skill-card.md file to streamline project documentation. - No cha","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 5.9K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s17aekq8k9ea9rzxqpwjjz8ea987ze4c:xrowgmbh-gitlab-hackathon","sourceUrl":"https://clawhub.ai/xrowgmbh/xrowgmbh-gitlab-hackathon","homepage":"https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/xrowgmbh/xrowgmbh-gitlab-hackathon","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":75,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, trackin"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T03:38:23.708Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T03:38:23.708Z","emptyReason":null},"stars":null,"forks":null,"downloads":5941,"packageName":null,"latestVersion":"1.108.1","tractionLabel":"5.9K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T03:38:23.707Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T03:38:23.708Z","lastCrawledAt":"2026-10-09T03:38:23.707Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T03:38:23.707Z","lastVerifiedAt":null,"highlights":[{"version":"1.108.1","createdAt":"2026-10-08T22:08:15.266Z","changelog":"- Removed the skill-card.md file to streamline project documentation. - No changes to core logic, descriptions, or workflows. - General maintenance update; no impact on functionality.","fileCount":3,"zipByteSize":4696},{"version":"1.108.0","createdAt":"2026-10-08T20:07:40.352Z","changelog":"- Removed the file skill-card.md from the project. - No changes made to primary skill documentation or logic. - Housekeeping update for file structure simplification.","fileCount":3,"zipByteSize":4632},{"version":"1.107.1","createdAt":"2026-10-08T18:09:17.762Z","changelog":"- Removed the skill-card.md file. - No changes were made to core skill logic or SKILL.md content.","fileCount":3,"zipByteSize":4644},{"version":"1.107.0","createdAt":"2026-10-08T17:05:10.516Z","changelog":"- Removed the file skill-card.md. - No changes were made to feature logic or documentation in SKILL.md.","fileCount":3,"zipByteSize":4809},{"version":"1.106.1","createdAt":"2026-10-08T10:18:08.610Z","changelog":"- Removed the file skill-card.md from the repository. - No user-facing functionality changes; documentation, usage, and scoring logic remain unchanged.","fileCount":3,"zipByteSize":4684},{"version":"1.106.0","createdAt":"2026-10-08T08:39:14.769Z","changelog":"- skill-card.md file removed. - No functional or documentation changes to the core skill content. - Structure and guidance in SKILL.md remains unchanged.","fileCount":3,"zipByteSize":4665},{"version":"1.105.1","createdAt":"2026-10-06T18:34:00.357Z","changelog":"- Removed the file: skill-card.md. - No other functional or documentation changes in this release.","fileCount":3,"zipByteSize":4632},{"version":"1.105.0","createdAt":"2026-10-06T16:29:53.292Z","changelog":"- Removed the file: skill-card.md - No user-facing changes to the skill logic or SKILL.md content.","fileCount":3,"zipByteSize":4645}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17aekq8k9ea9rzxqpwjjz8ea987ze4c:xrowgmbh-gitlab-hackathon","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T12:58:36.493Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrowgmbh-xrowgmbh-gitlab-hackathon/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T03:38:23.708Z","emptyReason":null},"readme":"Skill: GitLab Hackathon\n\nOwner: xrowgmbh\n\nSummary: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\n\nTags: latest:1.108.1\n\nVersion history:\n\nv1.108.1 | 2026-10-08T22:08:15.266Z | auto\n\n- Removed the skill-card.md file to streamline project documentation.\n- No changes to core logic, descriptions, or workflows.\n- General maintenance update; no impact on functionality.\n\nv1.108.0 | 2026-10-08T20:07:40.352Z | auto\n\n- Removed the file skill-card.md from the project.\n- No changes made to primary skill documentation or logic.\n- Housekeeping update for file structure simplification.\n\nv1.107.1 | 2026-10-08T18:09:17.762Z | auto\n\n- Removed the skill-card.md file.\n- No changes were made to core skill logic or SKILL.md content.\n\nv1.107.0 | 2026-10-08T17:05:10.516Z | auto\n\n- Removed the file skill-card.md.\n- No changes were made to feature logic or documentation in SKILL.md.\n\nv1.106.1 | 2026-10-08T10:18:08.610Z | auto\n\n- Removed the file skill-card.md from the repository.\n- No user-facing functionality changes; documentation, usage, and scoring logic remain unchanged.\n\nv1.106.0 | 2026-10-08T08:39:14.769Z | auto\n\n- skill-card.md file removed.\n- No functional or documentation changes to the core skill content.\n- Structure and guidance in SKILL.md remains unchanged.\n\nv1.105.1 | 2026-10-06T18:34:00.357Z | auto\n\n- Removed the file: skill-card.md.\n- No other functional or documentation changes in this release.\n\nv1.105.0 | 2026-10-06T16:29:53.292Z | auto\n\n- Removed the file: skill-card.md\n- No user-facing changes to the skill logic or SKILL.md content.\n\nv1.104.0 | 2026-10-06T15:27:48.827Z | auto\n\n- Removed the file skill-card.md from the repository.\n- No public-facing behavior or documentation in SKILL.md was changed.\n\nv1.103.0 | 2026-10-06T14:54:53.536Z | auto\n\n- Removed the file skill-card.md from the repository.\n- No changes to code or documentation functionality.\n- No SKILL.md or implementation changes included in this version.\n\nv1.102.0 | 2026-10-06T13:16:48.822Z | auto\n\nVersion 1.102.0\n\n- Removed the file: skill-card.md\n- No changes to functionality or documentation within SKILL.md.\n\nv1.101.0 | 2026-10-06T08:26:33.364Z | auto\n\n- Removed the skill-card.md file to simplify the repository.\n- No changes to core functionality or skill guidance.\n- Documentation, usage instructions, and scoring logic remain unchanged.\n\nv1.100.0 | 2026-10-05T21:33:24.703Z | auto\n\n- Removed the file skill-card.md.  \n- No changes to code or core skill logic; documentation and instructions remain unchanged.\n\nv1.99.1 | 2026-10-05T20:46:55.294Z | auto\n\n- Removed the file: skill-card.md.\n- No changes to skill functionality or instructions.\n- This update is a minor cleanup with no user-facing impact.\n\nv1.99.0 | 2026-10-05T17:51:16.354Z | auto\n\n- Removed the file skill-card.md.\n- No changes to code or functionality; documentation and skill description remain the same.\n\nv1.98.1 | 2026-10-05T14:46:50.347Z | auto\n\n- Removed the file skill-card.md.\n- No other functional or documentation changes.\n\nv1.98.0 | 2026-10-05T11:10:39.974Z | auto\n\n- Removed the file skill-card.md from the repository.\n- No changes were made to SKILL.md content or functionality.\n\nv1.97.1 | 2026-10-05T01:03:41.939Z | auto\n\n- Removed file: skill-card.md\n- No changes to SKILL.md content\n- No functional changes; only a documentation asset was deleted\n\nv1.97.0 | 2026-10-03T11:54:15.277Z | auto\n\n- Removed the skill-card.md file.\n- No user-facing changes to guides or instructions.\n- All functionality and documentation in SKILL.md remain unchanged.\n\nv1.96.0 | 2026-10-01T15:07:11.391Z | auto\n\n- Removed the file skill-card.md.\n- No functional or behavioral changes to the skill itself.\n\nv1.95.1 | 2026-10-01T14:01:04.296Z | auto\n\n- Removed file: skill-card.md\n- No changes to functionality or user-visible documentation\n- No new features or bug fixes in this version\n\nv1.95.0 | 2026-09-30T18:10:37.683Z | auto\n\n- Removed the file skill-card.md.\n- No changes to core logic or documentation other than the removed file.\n- All guidance and details in SKILL.md remain unchanged.\n\nv1.94.0 | 2026-09-24T05:09:07.620Z | auto\n\n- Removed the file skill-card.md from the project.\n- No user-facing feature or documentation changes in the main skill guide (SKILL.md).\n- No impact to functionality or hackathon process.\n\nv1.93.1 | 2026-09-23T21:54:11.975Z | auto\n\n- Removed the file skill-card.md.\n- No changes to functional logic or documentation in SKILL.md. \n- This update is a minor cleanup with no user-facing impact.\n\nv1.93.0 | 2026-09-20T05:54:24.261Z | auto\n\n- Removed the file skill-card.md.\n- No changes were made to the skill logic or documentation content.\n- This update cleans up redundant or unnecessary project files.\n\nv1.92.0 | 2026-09-19T19:16:24.530Z | auto\n\nVersion 1.92.0 of xrowgmbh-gitlab-hackathon\n\n- No file changes detected in this release.\n- No updates to documentation, functionality, or metadata.\n\nv1.91.8 | 2026-09-19T01:50:14.696Z | auto\n\n- No file changes detected in this release.\n- Skill version number incremented to 1.91.8.\n- All documentation, rules, and usage guidance remain unchanged from the previous release.\n\nv1.91.7 | 2026-09-18T18:25:17.461Z | auto\n\n- Removed the file skill-card.md.\n- No other functional or documentation changes.\n\nv1.91.6 | 2026-09-17T04:05:30.045Z | auto\n\nNo functional or documentation changes in this release.\n\n- Version 1.91.6 does not include any file changes.\n\nv1.91.5 | 2026-09-16T18:29:40.322Z | auto\n\n- Removed the file skill-card.md from the skill package.\n- No changes made to documentation or core functionality.\n\nv1.91.4 | 2026-09-16T07:21:10.182Z | auto\n\n- skill-card.md was removed.\n- No functional changes to the skill logic or documentation content.\n- The skill's core guidance, instructions, and structure remain unchanged.\n\nv1.91.3 | 2026-09-13T00:56:35.114Z | auto\n\n- Removed the file skill-card.md from the repository.\n- No other changes to skill logic, documentation, or workflow.\n- The skill’s functionality and user guidance remain unchanged.\n\nv1.91.2 | 2026-09-11T06:40:47.228Z | auto\n\n- Removed the file skill-card.md from the repository.\n- No changes were made to feature logic or user-facing documentation in SKILL.md.\n- Maintainers should note: Only file cleanup; no functional updates in this release.\n\nv1.91.1 | 2026-09-09T16:56:24.442Z | auto\n\n- Removed the file skill-card.md.\n- No changes were made to functionality or documentation within SKILL.md. \n- This release is a minor cleanup to project files only.\n\nv1.91.0 | 2026-09-09T13:54:02.632Z | auto\n\n- Removed the file: skill-card.md\n- No changes made to functionality or primary documentation.\n- Housekeeping update to streamline project files.\n\nv1.90.0 | 2026-09-08T06:41:57.496Z | auto\n\n- Removed the file skill-card.md.\n- No changes were made to the SKILL.md or implementation logic.\n- This update focuses solely on file cleanup and does not modify skill behavior or documentation.\n\nv1.89.0 | 2026-09-08T06:23:22.482Z | auto\n\n- Removed the file skill-card.md.\n- No changes to functionality or documentation content.\n- Maintains existing planning and fair participation guidance for GitLab hackathons.\n\nv1.88.0 | 2026-09-07T23:34:21.754Z | auto\n\n- Removed the file skill-card.md.  \n- No changes to core logic or user-facing documentation.  \n- Housekeeping update to remove unneeded metadata file.\n\nv1.87.0 | 2026-09-07T17:19:10.371Z | auto\n\n- Removed the file skill-card.md.\n- No other functional or documentation changes.\n\nv1.86.0 | 2026-09-07T08:24:11.737Z | auto\n\n- Removed the file skill-card.md from the repository.\n- No changes to core skill functionality or documentation in SKILL.md.\n\nv1.85.1 | 2026-09-07T06:29:45.558Z | auto\n\n- Removed the file skill-card.md.\n- No functional or documentation changes to the skill logic or usage instructions.\n- The skill continues to provide guidance for fair participation in GitLab hackathons.\n\nv1.85.0 | 2026-09-07T05:31:08.673Z | auto\n\n- Removed the file skill-card.md.\n- No changes made to documentation or core functionality.\n\nv1.84.7 | 2026-09-05T00:43:27.181Z | auto\n\n- Removed the file skill-card.md from the skill package.\n- No changes to functionality or documentation in SKILL.md.\n- Maintenance update only; no user-facing changes.\n\nv1.84.6 | 2026-09-03T00:15:25.211Z | auto\n\n- Removed the file skill-card.md.\n- No changes to skill functionality or documentation structure.\n- The skill documentation (SKILL.md) remains unchanged.\n\nv1.84.5 | 2026-09-02T00:33:24.770Z | auto\n\n- Removed the file skill-card.md from the project.\n- No changes to functionality or documentation content.\n- The skill's overall usage and workflow remain unchanged.\n\nv1.84.4 | 2026-09-01T10:42:49.165Z | auto\n\n- Removed the file skill-card.md.\n- No other changes to skill logic or documentation.\n\nv1.84.3 | 2026-09-01T08:28:33.629Z | auto\n\n- Removed the file skill-card.md.\n- No user-facing changes were made to the skill content or documentation.\n\nv1.84.2 | 2026-08-25T00:38:29.313Z | auto\n\n- Removed the file skill-card.md.\n- No other changes to functionality or documentation.\n\nv1.84.1 | 2026-08-24T20:11:26.458Z | auto\n\n- Removed the file skill-card.md.\n- No changes to code or the main skill documentation (SKILL.md contents unchanged).\n- No new features, bug fixes, or functional changes in this version.\n\nv1.84.0 | 2026-08-16T12:29:14.485Z | auto\n\n- Removed the file skill-card.md for simplification and file cleanup.\n- No changes to core logic, documentation, or functionality within SKILL.md.\n- Skill structure and usage remain unchanged for end users.\n\nArchive index:\n\nArchive v1.108.1: 3 files, 4696 bytes\n\nFiles: skill-card.md (2184b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.108.1:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.108.1:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.108.1\",\n  \"publishedAt\": 1791497295266\n}\n\nFile v1.108.1:skill-card.md\n\n## Description:\n\nPlan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to plan eligible hackathon contributions, prioritize reviewable merge requests, and check scoring and submission requirements while avoiding rule abuse.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: GitLab actions can modify public projects or affect hackathon scoring.\n\nMitigation: Use a least-privilege GitLab token and review merge requests, comments, labels, closures, and submissions before taking action.\n\nRisk: Outdated rules or ineligible activity can invalidate planned contributions.\n\nMitigation: Check current event rules, dates, eligibility, and prize submission requirements against official GitLab pages before acting.\n\n## Reference(s):\n\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [Current GitLab hackathon API](https://contributors.gitlab.com/api/v1/hackathons/current)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n- [ClawHub skill release](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Analysis, Markdown, Shell commands]\n\n**Output Format:** [Markdown with optional shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Recommendations depend on current hackathon rules and project status.]\n\n## Skill Version(s):\n\n1.108.1 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.108.0: 3 files, 4632 bytes\n\nFiles: skill-card.md (2006b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.108.0:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.108.0:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.108.0\",\n  \"publishedAt\": 1791490060352\n}\n\nFile v1.108.0:skill-card.md\n\n## Description:\n\nHelps contributors plan fair GitLab hackathon participation by checking rules, selecting qualifying issues and merge requests, tracking scoring, and avoiding rule abuse.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to plan eligible hackathon work, prioritize reviewable merge requests, and track participation without gaming scoring rules.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: GitLab commands or an overly privileged token could make unintended project changes.\n\nMitigation: Review commands before running them and use a least-privileged GitLab token.\n\nRisk: Incorrect labels, closures, comments, or merge requests could mislead maintainers or undermine fair participation.\n\nMitigation: Verify current event rules and keep project changes accurate, useful, and maintainable.\n\n## Reference(s):\n\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [Current GitLab Hackathon API](https://contributors.gitlab.com/api/v1/hackathons/current)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab Contribution Points Guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Shell commands]\n\n**Output Format:** [Markdown with optional shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Campaign brief, qualifying issue and merge request plan, scoring checks, and exploit watchlist.]\n\n## Skill Version(s):\n\n1.108.0 (source: ClawHub release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.107.1: 3 files, 4644 bytes\n\nFiles: skill-card.md (2036b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.107.1:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.107.1:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.107.1\",\n  \"publishedAt\": 1791482957762\n}\n\nFile v1.107.1:skill-card.md\n\n## Description:\n\nPlan fair GitLab hackathon participation by checking event rules, selecting qualifying contributions, tracking scoring opportunities, and documenting potential rule-abuse pitfalls.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to plan legitimate hackathon work, choose reviewable issues and merge requests, and check eligibility and submission requirements before acting.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Authenticated GitLab operations may expose or misuse account access.\n\nMitigation: Keep actions user-directed, limit access to GitLab credentials, and inspect the separate gitlab-agent skill before relying on it.\n\nRisk: Outdated event rules or scoring information may lead to ineligible contributions.\n\nMitigation: Verify current rules, dates, eligibility, and scoring against GitLab's event pages before acting.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Shell commands]\n\n**Output Format:** [Markdown with optional shell command snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Campaign briefs, contribution plans, and fair-use watchlists; no fixed output schema.]\n\n## Skill Version(s):\n\n1.107.1 (source: ClawHub release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.107.0: 3 files, 4809 bytes\n\nFiles: skill-card.md (2425b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.107.0:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.107.0:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.107.0\",\n  \"publishedAt\": 1791479110516\n}\n\nFile v1.107.0:skill-card.md\n\n## Description:\n\nPlan fair GitLab hackathon participation by checking event rules, choosing qualifying contributions, tracking scoring, and documenting potential rule-abuse edge cases.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to plan legitimate Quarterly or Transcend Hackathon entries, select reviewable issues and merge requests, and check eligibility before submitting work.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Overly broad GitLab token access could expose projects or allow unintended changes.\n\nMitigation: Use a least-privilege GitLab token for any GitLab operations.\n\nRisk: Proposed comments, labels, issue closures, or merge requests could be inaccurate or unfair.\n\nMitigation: Review each proposed action before posting and follow project and event rules.\n\nRisk: Hackathon eligibility, deadlines, and point values may change between events.\n\nMitigation: Confirm current event rules and scoring against official GitLab pages before acting.\n\nRisk: Exploit watchlist changes could be mistaken for approved tactics.\n\nMitigation: Approve watchlist edits explicitly and use them to avoid abuse or seek maintainer clarification.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n- [Current GitLab hackathon API](https://contributors.gitlab.com/api/v1/hackathons/current)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Shell commands]\n\n**Output Format:** [Markdown with optional shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Campaign briefs, contribution priorities, eligibility checks, and watchlist entries.]\n\n## Skill Version(s):\n\n1.107.0 (source: server-resolved release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.106.1: 3 files, 4684 bytes\n\nFiles: skill-card.md (2107b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.106.1:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.106.1:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.106.1\",\n  \"publishedAt\": 1791454688610\n}\n\nFile v1.106.1:skill-card.md\n\n## Description:\n\nPlan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to plan legitimate hackathon contributions, choose reviewable issues and merge requests, and check eligibility and scoring requirements.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: GitLab actions could post unwanted comments or make incorrect issue changes.\n\nMitigation: Review proposed public actions before posting, labeling, closing, or submitting.\n\nRisk: A GitLab token could grant unnecessary access.\n\nMitigation: Use a least-privileged GitLab token.\n\nRisk: Outdated event rules or scoring figures could lead to ineligible work.\n\nMitigation: Verify current requirements and point values against the linked official event pages before acting.\n\n## Reference(s):\n\n- [GitLab Hackathon skill release](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands]\n\n**Output Format:** [Markdown with inline shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Campaign brief, issue and merge request priorities, scoring checks, and exploit watchlist.]\n\n## Skill Version(s):\n\n1.106.1 (source: ClawHub release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.106.0: 3 files, 4665 bytes\n\nFiles: skill-card.md (2121b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.106.0:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.106.0:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.106.0\",\n  \"publishedAt\": 1791448754769\n}\n\nFile v1.106.0:skill-card.md\n\n## Description:\n\nPlan fair GitLab hackathon participation by checking current rules, choosing qualifying issues and merge requests, tracking scoring, and avoiding rule abuse.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal contributors and developers use this skill to plan legitimate GitLab hackathon contributions, select reviewable work, and check qualification and submission requirements before acting.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: A GitLab token may grant access beyond the contributions needed for a hackathon.\n\nMitigation: Use a token with the narrowest practical permissions and keep it private.\n\nRisk: Public merge requests, comments, labels, or issue closures may be inappropriate or fail event rules.\n\nMitigation: Confirm current rules and project permissions; make only legitimate, reviewable contributions and avoid spam or incorrect changes.\n\n## Reference(s):\n\n- [ClawHub skill listing](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [Current hackathon API](https://contributors.gitlab.com/api/v1/hackathons/current)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands]\n\n**Output Format:** [Markdown with inline bash code blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Plans and checklists should reflect current event rules and fair contribution practices.]\n\n## Skill Version(s):\n\n1.106.0 (source: server-resolved ClawHub release)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.105.1: 3 files, 4632 bytes\n\nFiles: skill-card.md (2057b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.105.1:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.105.1:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.105.1\",\n  \"publishedAt\": 1791311640357\n}\n\nFile v1.105.1:skill-card.md\n\n## Description:\n\nHelps contributors plan fair GitLab hackathon participation by checking rules, choosing qualifying issues and merge requests, tracking scoring, and avoiding rule abuse.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to check current hackathon requirements, choose reviewable contributions, and plan legitimate issue and merge-request activity.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: A GitLab token may grant broader access than hackathon work requires.\n\nMitigation: Use a least-privilege GitLab token.\n\nRisk: Comments, labels, issue closures, or merge requests may affect public projects.\n\nMitigation: Review each proposed action before posting and follow project rules.\n\nRisk: Hackathon dates, scoring, and eligibility requirements may change.\n\nMitigation: Confirm current requirements on the linked GitLab pages before participating.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands]\n\n**Output Format:** [Markdown with shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Plans and checklists for qualifying contributions; GitLab operations require glab, jq, curl, and a GitLab token.]\n\n## Skill Version(s):\n\n1.105.1 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.105.0: 3 files, 4645 bytes\n\nFiles: skill-card.md (1985b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.105.0:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.105.0:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.105.0\",\n  \"publishedAt\": 1791304193292\n}\n\nFile v1.105.0:skill-card.md\n\n## Description:\n\nHelps plan fair GitLab hackathon participation by checking current rules, choosing qualifying contributions, tracking scoring, and avoiding rule abuse.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and hackathon participants use this skill to plan reviewable GitLab contributions, confirm eligibility and deadlines, and track progress without manipulating engagement metrics.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: GitLab token access may expose projects or permit unintended actions.\n\nMitigation: Use a minimally scoped token and approve GitLab actions before execution.\n\nRisk: Automated engagement or issue changes may violate hackathon rules or disrupt maintainers.\n\nMitigation: Verify current rules and explicitly direct only fair, legitimate labeling, closing, commenting, and contribution activity.\n\n## Reference(s):\n\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [Current GitLab hackathon details](https://contributors.gitlab.com/api/v1/hackathons/current)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Analysis, Shell commands]\n\n**Output Format:** [Markdown with command examples and checklists]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Hackathon brief, contribution plan, and fair-use watchlist.]\n\n## Skill Version(s):\n\n1.105.0 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.104.0: 3 files, 4749 bytes\n\nFiles: skill-card.md (2278b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.104.0:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.104.0:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.104.0\",\n  \"publishedAt\": 1791300468827\n}\n\nFile v1.104.0:skill-card.md\n\n## Description:\n\nPlan fair GitLab hackathon participation by checking current rules, selecting qualifying issues and merge requests, tracking scoring opportunities, and avoiding rule abuse.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab hackathon participants use this skill to plan legitimate contributions, choose reviewable work, and check eligibility and deadlines before submitting merge requests or prize entries.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: A GitLab token may grant access beyond what the hackathon task requires.\n\nMitigation: Use a narrowly scoped token and review its permissions before running GitLab actions.\n\nRisk: Stale scoring, eligibility, or deadline guidance may lead to invalid entries.\n\nMitigation: Check the live hackathon rules and contribution points before acting.\n\nRisk: Incorrect labels, closures, comments, or merge requests can disrupt projects or appear publicly.\n\nMitigation: Review each proposed action for accuracy and relevance before posting or changing project records.\n\n## Reference(s):\n\n- [ClawHub skill release](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [GitLab current hackathon API](https://contributors.gitlab.com/api/v1/hackathons/current)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Analysis, Shell commands]\n\n**Output Format:** [Markdown with optional shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include a campaign brief, issue and merge request shortlist, and fair-use watchlist.]\n\n## Skill Version(s):\n\n1.104.0 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.103.0: 3 files, 4730 bytes\n\nFiles: skill-card.md (2273b), SKILL.md (7236b), _meta.json (146b)\n\nFile v1.103.0:SKILL.md\n\n---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friendly patch.\n- Keep the diff small.\n- Include a clear MR description with plan, acceptance criteria, and validation.\n- Run local checks and CI lint before pushing.\n- Respond to reviews quickly and resolve every thread.\n\n### 3. Compound\n\nAfter qualification is likely, add contributions that are legitimate and reviewable:\n\n- Open and merge additional small MRs during the window.\n- Link MRs to issues for the extra merged-with-issue credit.\n- Add useful comments only when they move work forward.\n- Label issues only when the label is correct.\n- Close issues only when they are duplicates, invalid, completed, or otherwise clearly closable.\n- Submit real events, content, translations, or AI catalog items only when they meet the published rules.\n\n## Scoring Levers\n\nVerify these values against the user guide before each event:\n\n- MR created: 20 points.\n- Commit merged: 20 points.\n- MR merged: 60 points, plus 30 more when linked to an issue.\n- Issue created: 5 points.\n- Issue labeled: 1 point.\n- Issue closed: 5 points.\n- Issue/MR comment: 1 point.\n- Discord message: 1 point; Discord reply: 2 points.\n- Forum post: 1 point; Forum reply: 2 points.\n- Event engagement: 500 points.\n- Content publication: 200 points.\n- Translation: 1 point.\n- AI catalog item version: 10 points.\n- Ad-hoc bonus: variable.\n\n## Issue and MR Selection\n\nPrefer work with all of these:\n\n- Clear owner, label, or maintainer signal.\n- Small blast radius.\n- Existing tests or an obvious validation path.\n- No dependency on secrets, production credentials, or protected branches.\n- A path to merge within the hackathon merge window.\n\nAvoid work with any of these unless there is a strong reason:\n\n- Unclear product direction.\n- Large migrations.\n- Inactive maintainers.\n- Required access you do not have.\n- CI known to be unstable without a workaround accepted by maintainers.\n\n## Transcend Hackathon\n\nBefore working on Transcend entries, re-open the live page and confirm current requirements.\nAs of the 2026 event page, the Transcend Hackathon runs June 10-24, 2026 UTC, focuses on\nAI-native contributions to GitLab's Knowledge Graph, and requires both registration and\nDevPost submission for cash prizes.\n\nWhen choosing a Transcend path:\n\n- For the Contribute track, select labeled Knowledge Graph issues and submit focused MRs.\n- For agent/workflow entries, build a working demo with clear setup, test evidence, and a short explanation of how it uses the Knowledge Graph.\n- Keep prize submission artifacts reproducible: repository link, demo instructions, screenshots or video, and a concise impact statement.\n\n## Exploit Watchlist\n\nTrack edge cases discovered during research or execution. Use them to avoid accidental rule abuse\nand to ask maintainers for clarification when needed.\n\n- Qualification gate: Quarterly Hackathon points can become zero if no MR merges before the deadline.\n- Timing edge: MRs must be opened during the hackathon window; opening too early may not qualify.\n- Merge deadline edge: MRs merged after the post-hackathon merge window may not count.\n- Commit-count edge: commits score only when merged; do not pad or fragment commits just for points.\n- Comment edge: comments score, but spam comments harm reviewers and may be disqualified.\n- Label/close edge: labels and closures score, but incorrect labels or invalid closures are unfair and create cleanup work.\n- Linked-issue edge: linked MRs get extra credit; only link to real, relevant issues.\n- Event/content edge: high point values require genuine eligible activity, not placeholder submissions.\n- Transcend prize edge: leaderboard activity alone may not satisfy DevPost or registration requirements.\n\nWhen a new edge case appears, append it here with:\n\n- Source link.\n- Observed behavior.\n- Fair-use decision.\n- Whether maintainers need to be notified.\n\n## End-of-Run Checklist\n\n- At least one qualifying MR merged or on track to merge.\n- Every MR links to a real issue when possible.\n- CI passes on all active MRs.\n- Review threads are resolved.\n- Time spent and useful status comments are recorded in GitLab.\n- Leaderboard position and scoring mix are checked.\n- Any exploit-like behavior is documented in the watchlist and avoided unless maintainers explicitly approve it.\n\nFile v1.103.0:_meta.json\n\n{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.103.0\",\n  \"publishedAt\": 1791298493536\n}\n\nFile v1.103.0:skill-card.md\n\n## Description:\n\nPlan fair GitLab hackathon participation by checking event rules, selecting qualifying issues and merge requests, tracking scoring, and avoiding rule abuse.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to plan legitimate hackathon entries, prioritize reviewable work, and check eligibility and scoring before submitting contributions.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: GitLab actions performed with a token may change issues or merge requests.\n\nMitigation: Review commands before execution, especially comments, labels, issue closures, and merge request creation.\n\nRisk: Event dates, eligibility requirements, and scoring values may change.\n\nMitigation: Check the current event pages and contribution points guide before planning or submitting work.\n\nRisk: Optimizing for points can produce spam or invalid contributions.\n\nMitigation: Submit genuine work, link only relevant issues, and avoid padded commits, spam comments, and unsupported labels or closures.\n\n## Reference(s):\n\n- [ClawHub skill listing](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n- [Quarterly GitLab Hackathon](https://contributors.gitlab.com/hackathon)\n- [Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n- [Current hackathon API](https://contributors.gitlab.com/api/v1/hackathons/current)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Guidance]\n\n**Output Format:** [Markdown with optional shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Campaign briefs, issue and merge request priorities, scoring checks, and an exploit watchlist.]\n\n## Skill Version(s):\n\n1.103.0 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.","readmeExcerpt":"Skill: GitLab Hackathon Owner: xrowgmbh Summary: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist. Tags: latest:1.108.1 Version history: v1.108.1 | 2026-10-08T22:08:15.266Z | auto - Removed the skill-card.md file to streamline project documentation. - No cha","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"curl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq ."},{"language":"bash","snippet":"curl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'"},{"language":"bash","snippet":"curl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq ."},{"language":"bash","snippet":"curl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'"},{"language":"bash","snippet":"curl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq ."},{"language":"bash","snippet":"curl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: gitlab-hackathon\ndescription: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\", \"jq\", \"curl\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Hackathon Skill\n\nUse this skill to compete fairly in GitLab hackathons with a repeatable, evidence-based plan.\nPrioritize real contributions that reviewers can merge quickly. Do not spam comments, pad commits,\nmislabel issues, or close issues without a valid reason.\n\nFor GitLab operations, read and follow the `gitlab-agent` skill.\n\n## Quick Start\n\n1. Verify the current rules, dates, tracks, and prize requirements:\n   - Quarterly Hackathon: `https://contributors.gitlab.com/hackathon`\n   - Current hackathon API: `https://contributors.gitlab.com/api/v1/hackathons/current`\n   - Transcend Hackathon: `https://contributors.gitlab.com/transcend-hackathon`\n   - Contribution points: `https://contributors.gitlab.com/docs/user-guide#contribution-points`\n2. Confirm eligibility before optimizing:\n   - Quarterly Hackathon scoring requires at least one qualifying merge request to be merged.\n   - Quarterly Hackathon MRs must be opened during the 7-day hackathon window and merged before the merge deadline.\n   - Transcend Hackathon cash prizes require registration and a DevPost submission; verify the current page before starting.\n3. Pick work that can merge:\n   - Prefer quick-win issues, small bugs, documentation fixes, tests, and self-contained components.\n   - Prefer issues with clear reproduction, clear acceptance criteria, and recent maintainer activity.\n   - Avoid huge refactors, ambiguous product decisions, flaky areas, and changes that need protected-branch access.\n4. Create a small qualifying MR first, then scale:\n   - Link every MR to an issue when possible.\n   - Keep each MR reviewable, tested, and easy to merge.\n   - Ask for review through the project workflow only after CI passes and discussions are resolved.\n\n## Fair Winning Plan\n\n### 1. Analyze\n\nBuild a one-page campaign brief before coding:\n\n- Hackathon name, UTC start/end, merge deadline, prize requirements, and qualifying projects.\n- Tracks and labels that matter, including `Hackathon`, `quick-win`, or Transcend-specific labels.\n- Current leaderboard leaders and their scoring mix.\n- Personal constraints: available time, project permissions, and trusted language/tooling areas.\n\nUseful commands:\n\n```bash\ncurl -sS https://contributors.gitlab.com/api/v1/hackathons/current | jq .\nglab api '/projects/:fullpath/issues?labels=quick-win&state=opened&per_page=50'\nglab api '/merge_requests?state=opened&scope=created_by_me&per_page=100'\n```\n\n### 2. Qualify\n\nSecure at least one merged MR early. This unlocks scoring for the Quarterly Hackathon and reduces\nthe risk of finishing with zero points.\n\n- Choose a low-risk issue with a maintainer-friend"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n  \"slug\": \"xrowgmbh-gitlab-hackathon\",\n  \"version\": \"1.108.1\",\n  \"publishedAt\": 1791497295266\n}"},{"path":"skill-card.md","content":"## Description:\n\nPlan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrowgmbh](https://clawhub.ai/user/xrowgmbh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nGitLab contributors use this skill to plan eligible hackathon contributions, prioritize reviewable merge requests, and check scoring and submission requirements while avoiding rule abuse.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: GitLab actions can modify public projects or affect hackathon scoring.\n\nMitigation: Use a least-privilege GitLab token and review merge requests, comments, labels, closures, and submissions before taking action.\n\nRisk: Outdated rules or ineligible activity can invalidate planned contributions.\n\nMitigation: Check current event rules, dates, eligibility, and prize submission requirements against official GitLab pages before acting.\n\n## Reference(s):\n\n- [GitLab Quarterly Hackathon](https://contributors.gitlab.com/hackathon)\n- [Current GitLab hackathon API](https://contributors.gitlab.com/api/v1/hackathons/current)\n- [GitLab Transcend Hackathon](https://contributors.gitlab.com/transcend-hackathon)\n- [GitLab contribution points guide](https://contributors.gitlab.com/docs/user-guide#contribution-points)\n- [ClawHub skill release](https://clawhub.ai/xrowgmbh/skills/xrowgmbh-gitlab-hackathon)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Analysis, Markdown, Shell commands]\n\n**Output Format:** [Markdown with optional shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Recommendations depend on current hackathon rules and project status.]\n\n## Skill Version(s):\n\n1.108.1 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist. Skill: GitLab Hackathon Owner: xrowgmbh Summary: Plan and execute fair GitLab hackathon participation, including Quarterly and Transcend Hackathons, by analyzing rules, selecting qualifying issues/MRs, tracking scoring levers, and keeping an exploit watchlist. Tags: latest:1.108.1 Version history: v1.108.1 | 2026-10-08T22:08:15.266Z | auto - Removed the skill-card.md file to streamline project documentation. - No cha","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1163,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T03:38:23.708Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T03:38:23.708Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:58:36.496Z","emptyReason":null},"items":[{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-10T18:48:31.762Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}