CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 1 flagged

Securityscore 88 · 1 finding

MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · plugins/kotlin-multiplatform/skills/kmp-interop-bridges/SKILL.md

MEDIUM — it fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.

Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted

excerptplugins/kotlin-multiplatform/skills/kmp-interop-bridges/SKILL.md· markdown

24- Use `iosMain` for Apple-family code covering iOS device/simulator.

25- SDK bootstrapping, lifecycle, and packaging stay in platform app modules.

26- Do not leak Android/UIKit/Foundation/POSIX/vendor SDK types into shared domain contracts u

… (27 chars elided on L26)

28## Swift API

Occurrences

1 occurrence · at L26

How to fix

Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.

Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-IMPERATIVE-01sha256838948ee08b3eb67…rubric 365aacaView on GitHub

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

plugins/kotlin-multiplatform/skills/kmp-interop-bridges/SKILL.md · 1 file

plugins/kotlin-multiplatform/skills/kmp-interop-bridges/SKILL.md2.9 KB · Markdown

name: kmp-interop-bridges

description: Design and review KMP platform bridges, source-set placement, expect/actual, entry-point wiring, cinterop, Swift API readiness, SKIE, KMP-NativeCoroutines, KDoctor, XCFrameworks, and SwiftPM export.

KMP Interop Bridges

Use for KMP bridges, shared-native boundaries, Swift/native export reviews.

Decision Order

commonMain if no platform API needed.
Existing multiplatform library if one covers it.
Intermediate source set, such as iosMain, for one shared implementation.
Common interface plus platform entry-point wiring if cleaner.
Narrow expect/actual function or property if enough.
Consider broader expect/actual classes or generated interop only after 1-5 fail.

Do not default to expect/actual for every platform dependency.

Source Sets

Use highest valid source set.
Use iosMain for Apple-family code covering iOS device/simulator.
SDK bootstrapping, lifecycle, and packaging stay in platform app modules.
Do not leak Android/UIKit/Foundation/POSIX/vendor SDK types into shared domain contracts unless intentionally public.

Swift API

Review:

Kotlin Flow, StateFlow, suspend functions.
sealed classes/interfaces, enums.
default arguments, overload ergonomics.
Kotlin collections, nullability, error handling.
package/module names, framework baseName.
binary framework static/dynamic choice.
exported dependencies; intentional transitiveExport.

SKIE can improve Swift ergonomics via wrappers for Flow, suspend functions, sealed hierarchies, enums, and default arguments. Optional: verify current docs, build impact, team acceptance, generated API before adding.

KMP-NativeCoroutines can expose flows to Swift; choose only after comparing current project needs, existing API shape, and docs.

cinterop

Check .def, headers, package names, include directories, compiler/linker options, and architecture support.
Prefer Objective-C-compatible APIs for Swift/Apple dependencies unless current Kotlin tooling supports the needed Swift import route.
Put generated bindings behind project-owned facades when possible.
Validate simulator/device architectures.

Environment

If host setup may be at fault, consider KDoctor on macOS. It checks KMP mobile readiness: OS, JDK/JAVA_HOME, Android Studio plugins, Xcode, Ruby, CocoaPods. Do not treat output as project architecture review.

SwiftPM/XCFramework

Remote iOS:

Build XCFramework for Apple targets.
Validate Package.swift.
Calculate/update checksum for binary targets.
Use semantic version tags for SwiftPM consumers.
Test import in Xcode.
For multiple KMP modules, consider umbrella module and state exported dependencies.
Use Swift wrapper target when a binary target must travel with Swift-only dependencies.
Consider KMMBridge only when the team wants maintained prebuilt-framework publishing; verify spm()/cocoapods() mode, artifact hosting, versioning, consumer docs.

kmp-interop-bridges— agent skill

Is kmp-interop-bridges safe to install?

KMP Interop Bridges

Decision Order

Source Sets

Swift API

cinterop

Environment

SwiftPM/XCFramework

Audit the pieces. Scan the whole. Decide.