Digital Twin

v1.0.2

Build a psychologically grounded Digital Twin personality skill from Fireflies meeting transcripts. Use this skill whenever the user asks to create a digital...

0· 54·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (build a Digital Twin persona from Fireflies transcripts) matches what the SKILL.md instructs: retrieve transcripts via the user's Fireflies connector, analyze linguistic/psychometric/judgment/audience pillars, and emit an installable personality skill. There are no unrelated env vars, binaries, or install steps requested.
Instruction Scope
The SKILL.md is highly prescriptive and stays within the stated purpose, but it depends on calling the user's separate Fireflies skill/connector to fetch transcripts and repeatedly asserts that raw transcripts 'are not persisted, exported, or transmitted' — that is an instruction-level claim the agent must follow, not something verifiable from the bundle. The skill asks the agent to extract only the target person's contributions and to require user-confirmed consent before proceeding; this is good practice but cannot be enforced by the static skill bundle itself. Also note the SKILL.md is long and references generating additional files (audience_profiles.md, etc.) that are expected to be produced as part of the output.
Install Mechanism
No install spec and no code files — instruction-only skill. That minimizes supply-chain risk because nothing is downloaded or executed by default.
Credentials
The skill declares no required credentials, env vars, or config paths. It explicitly depends on the user having a separately configured Fireflies connector; any credentials belong to that other connector, not to this skill. This is proportionate to the stated functionality.
Persistence & Privilege
always:false (normal). The skill can be user-invoked and the agent may call it autonomously (platform default). The workflow produces an 'installable personality skill' that, if installed/enabled, could be used persistently to impersonate a person — this is a capability aligned with the skill goal but raises privacy/ethical considerations the operator should evaluate before enabling persistent or session-global use.
Assessment
This skill appears coherent with its purpose, but review these before installing or using: - Consent & legality: The skill can produce an installable persona that mimics a real person. Only build personas for people who have given explicit consent; check company policy and local law about impersonation and personal data processing. - Trust the connector: The skill depends on your separate Fireflies connector to fetch transcripts. Ensure that connector is properly scoped, audited, and only returns the transcripts you expect. The digital-twin skill's claim that it won't persist or transmit raw transcripts is an instruction — verify behavior by testing with your own transcripts first. - Secrets & access: This skill asks for no creds itself, but the Fireflies connector you use will have credentials — follow least privilege for that connector and review its logs/permissions. - Review generated output: The skill will produce an installable personality SKILL.md and supporting files that enable impersonation. Before installing a generated persona into production or enabling it persistently, inspect the generated skill for overly broad behaviors, sensitive content inclusion, or scope creep. - Start small: Test the workflow using transcripts of yourself or consenting colleagues, inspect outputs, and confirm you can revoke or remove any generated persona. If you want a stronger assessment, provide the untruncated parts of SKILL.md (the runtime workflow was truncated) or example transcripts and a generated persona so I can check whether any steps read or transmit unexpected paths, environment variables, or external endpoints.

Like a lobster shell, security has layers — review code before you run it.

latestvk971gnd6vb6jn4bb6k3vce0efh84xpc1

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments