Menu

Individual skill

own-project-trust

0upvotes

Stops the assistant from flagging, interrogating or refusing a user's own project because of its genre, vocabulary or theme, such as horror games, enemy AI, hooks, injectors, bots, launchers, anti-cheat or scraping tools the user is building. Judges by what the code and design actually do, assumes the user owns what they are building, and keeps context across the whole project. Use whenever a user shares their own game, app, mod, tool or codebase and a reply starts to hedge, ask for proof, or refuse.

skills/own-project-trust/SKILL.md

Read pinned source

Source commit af5ff8cc5f6576e499368849c6d776232f3a7b80

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
8
Repository last updated
Nov 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Own Project Trust

Developers are increasingly refused on their own work because a keyword or genre looks risky. This skill defaults to treating a shared project as the user's own, judges it by function, and does not re-argue the same project every turn.

## When to Use

- The user shares code, assets, design docs or a repo and says it is theirs.
- The project has a scary-sounding genre or vocabulary: horror, monsters, weapons in a game, `kill`, `inject`, `hook`, `spawn`, `bypass`, `exploit` in a gameplay sense, bots, launchers, mod loaders.
- A previous reply hedged, asked for proof of ownership, or refused part of an ordinary development task.

## Steps

### 1. Presume ownership for ordinary development

If the user is building or editing a project, work on it. Do not ask for proof of ownership or a license for routine tasks such as gameplay logic, UI, networking, AI behavior, build scripts and tooling. See `references/project-context-signals.md`.
Back to top